🚀 go-pugleaf

Yes, Remy.  I understand.

It's a strange contract since the Cleanup Manager window is quite small.

Thanks for your input.

-- 
Malcolm Smith
MJ Freelancing
http://www.mjfreelancing.com

Associate Editor
C++Builder Developers Journal
http://www.bcbjournal.com


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:44636b16@newsgroups.borland.com...
>
> "Malcolm Smith" <mjfreelancing@optusnet.com.au> wrote in message
> news:44631fb8$1@newsgroups.borland.com...
>
>> It turned out to be incorrect behaviour - my form become embedded
>> in the cleanup manager (as described in the help file).
>
> That is what it is supposed to do.  A window can't have a parent window 
> and
> still be its own top-level window.  If you need your dialog window to 
> remain
> its own popup window, then you have to use a NULL parent window.  But then
> your popup window won't have any ties to the Cleanup Manager's window.
>
>> Is there any way I can make the cleanup manager auto
>> minimize/restore if a user minimizes my form ?
>
> If your DLL is passed in an HWND parent window, you need to use it as a
> parent window.  That is the contract that the DLL needs to follow, since
> that is the way the interface is spec'ed out to operate.
>
> With that said, one thing you can consider doing is to have 
> ShowProperties()
> call EnumWindows() and GetWindowThreadProcessId() to build up a list of 
> all
> the HWND handles that belong to the calling process.  When your popup form
> is minimized/restored, you can run through the list minimizing/restoring
> those windows as needed.  In order to detect when the user
> minimizes/restores those windows directly, you would have to subclass them
> via SetWindowLong(GWL_WNDPROC) to catch all messages that are issued to
> them.
>
>
> Gambit
>
>