RE: [GD-Windows] Messed up windows after fullscreen
Brought to you by:
vexxed72
From: Philip T. <pt...@mi...> - 2001-10-03 01:55:39
|
> -- Perhaps an online up to the minute column (maintained by=20 > someone at MS,perhaps Phil?) of "now" what is the correct way to = handle=20 > deactivate, and what kind of things would be lose, and how to handle = them,=20 > (and the creation loop again, and the shutdown process again) for each = relevant=20 > version of Windows OS version. sorry, but I am way too busy with DX issues to volunteer for this one. > -----Original Message----- > From: Corrinne Yu [mailto:cor...@sp...] > Sent: Tuesday, October 02, 2001 2:21 PM > To: gam...@li... > Subject: Re: [GD-Windows] Messed up windows after fullscreen >=20 >=20 > ----- Original Message ----- > From: "Philip Taylor" <pt...@mi...> > To: <gam...@li...> > Sent: Tuesday, October 02, 2001 3:39 PM > Subject: RE: [GD-Windows] Messed up windows after fullscreen >=20 >=20 > any good introductory Win32 tome should discuss, somewhat, the > initialization sequence of messages duing window creation. serious > spelunkers should be familiar with Matt Pietreks' work. >=20 > -- The bad thing is that by the time the next Matt P. book is=20 > on the shelf, > new windows messages, and message proc behaviors, for newer=20 > versions of > windows, already make some of it obsolete. >=20 > -- It eventually comes down to trial and error shared among=20 > programmers, > word of mouth with Microsoft engineers, and sometimes=20 > Microsoft seminars, on > a continual cycle. >=20 > -- This applies more to the whole "activate" "losing context"=20 > situation than > for "creation." >=20 > -- Perhaps an online up to the minute column (maintained by=20 > someone at MS, > perhaps Phil?) of "now" what is the correct way to handle=20 > deactivate, and > what kind of things would be lose, and how to handle them,=20 > (and the creation > loop again, and the shutdown process again) for each relevant=20 > version of > Windows OS version. >=20 > -- May be more contemporary. >=20 > Corrinne >=20 > P.S. It is not too bad, usually it is no more than a few=20 > lines of code to > add or change everytime new OS changes. The "bad" would be for already > released applications that doesn't get patched. >=20 >=20 > _______________________________________________ > Gamedevlists-windows mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows >=20 |