The trick is in Sub-Classing or Super-Classing your controls so that they use your own WndProc() instead of the default.
- Chris
Not many can claim 25 years on the Internet! Join us in celebrating this milestone. Learn more about our history, and thank you for being a part of our community!
The trick is in Sub-Classing or Super-Classing your controls so that they use your own WndProc() instead of the default.
- Chris
Thanks
Ok, i hope my english is comprehensive, and sorry for fault...
Thanks,
Xas
The first way is what you described - basically bending the Win32 API to support cool GUI stuff. This might mean using bitmaps as window backgrounds, subclassing controls, etc. Goods: (Presumably) less code than the other method. Bads: There are some things that are practically impossible to do (alpha blts), and you have to deal with the sluggishness of GDI.
The second way is to just create a windowed DirectDraw app and then strip off its title bar. Pluses: By using DDraw, you can do anything - complex animation, nifty alpha effects, etc. Minuses: Lots of code. You've got to redo most of the GUI processing (animating the button clicks, figuring out what button the moues cursor hit, etc). If you go this way, my GUI articles should be able to help you.
It *might* be possible to use some bizarre combination of (invisible) controls and windowed DirectDraw, so as to trick Windows into sending you the correct WM_COMMANDs, but I've never done it, so I don't know how difficult it would be.
Hope it helps...
Mason McCuskey
Spin Studios
www.spin-studios.com