Using: internal delegate int WindowEnumProc(IntPtr hwnd, IntPtr lparam); DllImport("user32. Dll") internal static extern bool EnumChildWindows(IntPtr hwnd, WindowEnumProc func, IntPtr lParam); you will get callbacks on the function you pass in.
Use EnumChildWindows, with p/invoke. Here's an interesting link about some of it's behavior: blogs.msdn.com/oldnewthing/archive/2007/... If you don't know the handle of the window, but only it's title, you'll need to use EnumWindows. pinvoke.net/default.aspx/user32/EnumWind....
Here is a managed alternative to EnumWindows, but you will still need to use EnumChildWindows to find the handle of the child window. Foreach (Process process in Process.GetProcesses()) { if (process. MainWindowTitle == "Title to find") { IntPtr handle = process.
MainWindowHandle; // Use EnumChildWindows on handle ... } }.
I'm trying to do this, but there is no main window for the process. – Epu Oct 7 at 14:47 Epu, if there is not a main window then the process will not have a window handle to obtain (ie. Process.
MainWindowHandle == IntPtr. Zero). – Special Touch Oct 7 at 21:31.
I've found the best solution to be Managed WindowsAPI. It had a CrossHair control that could be used to select a window(not part of the question), and a method AllChildWindows to get all child windows which likely wrapped the EnumChildWindows function. Better not to reinvent the wheel.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.