![]() |
| [[ Home | Forums | 3D Engines Database | Wiki | Articles/Tutorials | Game Dev Jobs | IRC Chat Network | Contact Us ]] |
|
|
#1 |
|
New Member
Join Date: Dec 2004
Location: Hungary
Posts: 4
|
Every DX tutorial series begins with the intruduction of the necessary WIN32 API basics usually. Also, all of them mentions window classes, when it it really unnecessary IMHO. You can specify the predefined "STATIC" as window class, it will have the same effect. Window classes have their uses( well, only sindgle app instance forcing maybe ), but in this context its a bunch of unneeded info I think.
|
|
|
|
|
|
#2 |
|
DevMaster Staff
Join Date: Sep 2003
Location: Hell
Posts: 1,109
|
would'nt a static window be one that cannot be moved, and which has a pre-defined windows handler, and which you cannot the frame off and which you can't make use of the cb[Cls/Wnd/]Extra options?
Granted you can do all that with *other functions* after creating a static function, but putting in the info for all those other functions to get a little control over your window is, i feel, unneeded complexity. |
|
|
|
|
|
#3 |
|
DevMaster Staff
Join Date: Oct 2004
Location: Seattle, WA
Posts: 3,707
|
Yeah. Window classes are definitely useful, if for no other reason than the 'lpfnWndProc' member
![]()
___________________________________________
Currently working at Sucker Punch reedbeta.com - OpenGL demos and other projects Luabridge - a lightweight, dependency-free C++/Lua binding library. CD Lite - an unobtrusive, minimal CD player application for Windows. |
|
|
|
|
|
#4 |
|
Valued Member
Join Date: Aug 2005
Posts: 162
|
Reedbeta: heh, i prefer snatching the window-messages in the message-pump instead
![]() |
|
|
|
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|