RE: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE

[Brian H. <bri...@py...>]

Yep.  DefWindowProc() gets called on all messages except the ones it
shouldn't =) (specifically, WM_CREATE, WM_DESTROY and WM_ERASEBKGND).

Brian

> -----Original Message-----
> From: gam...@li... 
> [mailto:gam...@li...] On 
> Behalf Of Andrew Grant
> Sent: Tuesday, January 29, 2002 3:57 PM
> To: gam...@li...
> Subject: Re: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE
> 
> 
> Do you call DefWindowProc at the bottom of your message loop?
> 
> 
> // andrew
> 
> ----- Original Message ----- 
> From: "Brian Hook" <bri...@py...>
> To: <gam...@li...>
> Sent: Tuesday, January 29, 2002 11:39 PM
> Subject: RE: [GD-Windows] WA_CLICKACTIVE vs. WM_MOUSEACTIVATE
> 
> 
> > > Oddly enough, I'm also not receiving WA_CLICKACTIVE in
> > > WM_ACTIVATE...curiouser and curiouser.
> > 
> > Okay, it's gone from curious to annoying.  If I click on my app's 
> > title bar, I get WM_MOUSEACTIVATE and 
> WM_ACTIVATE/WA_CLICKACTIVE.  If 
> > I click in the client area, however, I only get 
> WM_ACTIVATE/WA_ACTIVE.  
> > It's a pretty vanilla window.  The only thing I can think 
> of is that 
> > some of the documentation throws around "Child window" as a term a 
> > lot, and since the only child windows I have are created by Windows 
> > (title bar, system menu), that my problem lies with that.
> > 
> > Brian
> > 
> > 
> > _______________________________________________
> > Gamedevlists-windows mailing list 
> > Gam...@li...
> > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows
> > 
> 
> 
> _______________________________________________
> Gamedevlists-windows mailing list 
> Gam...@li...
> https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows
>