RE: [GD-Windows] Finding HWND of the current thread

[Donavon K. <kei...@ea...>]

Actually both windows would get WM_ACTIVATEAPP, even if they're different
window classes, so let me change my bet... :-)

Perhaps it's sufficient that the window be top-level?

Donavon Keithley


-----Original Message-----
From: Donavon Keithley [mailto:kei...@ea...] 
Sent: Thursday, July 15, 2004 2:30 PM
To: 'gam...@li...'
Subject: RE: [GD-Windows] Finding HWND of the current thread

> God knows what the HWND is really used for in DirectSound and 
> what can happen if you do something like create a hidden window 
> and bind DS to that instead of to your real application window.

I would imagine that it's subclassing the window and sniffing for
deactivation while in exclusive mode, as D3D does with the "focus" window.
That would imply that it needs to be top-level and that the choice of window
is quite significant.  For instance in a D3D app, it should be the same
window as the D3D focus window.

As an experiment, I'd create a test app with two top-level windows.  Give
one to D3D and the other to DSound, go exclusive on both, and see what
happens when you Alt-Tab away.  Will DSound realize that it should
relinquish?  I don't have a lot of experience with DSound, but my chips are
on "no".

Donavon Keithley