Re: [GD-Windows] IsIconic() vs. trapping window messages

[Corrinne Y. <cor...@sp...>]

You definitely want to still hook into
WM_SIZE where wParam == SIZE_MAXHIDE.

You are not minimized, but some other window is covering yours, because they
are maximized.






----- Original Message -----
From: "Brian Hook" <bri...@py...>
To: <gam...@li...>
Sent: Friday, November 09, 2001 2:34 PM
Subject: [GD-Windows] IsIconic() vs. trapping window messages


> I've seen two different ways of detecting minimized state.  The first is
> the standard trapping of WM_MOVE, WM_SIZE, WM_ACTIVATE, etc. messages.
> However, I've seen other code that uses IsIconic(HWND).  The latter
> obviously can't provide you the state change detection, but assuming you
> don't need to capture a change in state but only need to know if you're
> iconic or not, is there any place where IsIconic() will fail?
>
> For example, a game might only need to know if it's active or not, and
> whether to render.  Activation can be handled through the usual
> suspects, and the render loop could just do:
>
> if ( active && !IsIconic( hwnd ) )
>    render();
>
> ...instead of all the cruft that normally goes into the WndProc.
>
>
>
> _______________________________________________
> Gamedevlists-windows mailing list
> Gam...@li...
> https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows
>