ralph
9/2/2010 3:18:00 AM
On Wed, 01 Sep 2010 18:05:27 -0700, Karl E. Peterson <karl@exmvps.org>
wrote:
>Sneha Menon pretended :
>>> Almost certainly, nothing. Windows will just attempt to "close
>>> nicely", presumably by sending WM_CLOSE to the top-level window, all
>>> apps in that group.
>>
>> That's what I had thought. And, as almost all the projects I had
>> handled was single instance ones I hadn't done any research into it.
>>
>> But One of my applications(a custom browser, Multiple instances of
>> it), it is not responding to 'Close Group' calls. Nothing happens when
>> I click 'Close Group'
>>
>> The application does not have a mdi form.
>> The Main form does not have a conventional title bar. An activeX
>> component (w/ icon, caption, min button, close button, customizable
>> gradient BG) serve as the title bar.
>> No any code in QueryUnload event.
>>
>> What could be the possible reasons? Ralph was mentioning queryunload,
>> but I could not see anything in the post addressing the 'close group'
>> issue. Is there anything I can do in the QueryUnload to make the
>> application close all its instances?
>
>Well, you could certianly try it, but given you don't have a standard
>titlebar I'm starting to suspect that your app isn't processing
>WM_CLOSE at all. What happens when you have a single instance, and
>just select "Close" from the right-click on the taskbar menu?
>
>Since you've chosen to use a non-standard UI, odds are you're going to
>need to do some message sniffing with Spy++ and probably subclass the
>hidden top-level window watching for WM_CLOSE. But your use of the 3rd
>party tool really means only you can troubleshoot this one.
Why is all the really interesting information always so late in
coming?
-ralph
<g>