🚀 go-pugleaf

"David" <david@pedley.ws> wrote in message
news:46385cda$1@newsgroups.borland.com...

> I have tried using EnumWindows() and GetWindowThreadProcessId()
> to enumerate all of the 'top level' threads/processes active on the
workstation
> (a large number). However, none of these matches the thread or
process ids
> returned by the CreateProcess().

Yes, they will.  Please show your actual code.  I would also suggest
calling WaitForInputIdle() before calling EnumWindows(), to give the
new process some time to create and show its windows.

> Is it possible that the new process was created as a child of
something?
> I was running the test from the IDE.

No.  That wouldn't matter anyway, since you have the IDs of the new
process itself.  Each window belongs to a specific process, even if it
were a child process.

> Incidentally, had somewhat of a struggle to get the callback to
> EnumWindows() working. The first parameter of EnumWindows
> is a pointer to the callback routine which is defined as
> WNDENUMPROC, which in turn is defined as
>
>      int __stdcall CbFunction ()
>
> whereas the callback routine required is actually
>
>      int __stdcall CbFunction (HWND w, LPARAM parm)
>
> This means defining the latter and casting its pointer to the former
> when specifying the EnumWindows parameter

Yes.

> hardly sophisticated practice.

No, but it is required practice in this particular case.  Just one of
many quirks in how the Win32 API operates in general.

> Is this a bug in the header files

No.


Gambit