• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
ATC

Why does CreateWindowW fail?

28 posts in this topic

Hmmm, that did it... WTF lol...

Is it acceptable to just redefine my WndProc like so:

[source lang="cpp"]
LRESULT Window::WndProc( UInt32 msg, WPARAM wParam, LPARAM lParam ) {

HDC hDC;
PAINTSTRUCT paintStruct;

switch( msg )
{
case WM_PAINT:
hDC = BeginPaint( this->hWnd, &paintStruct );
EndPaint( this->hWnd, &paintStruct );
break;

case WM_SIZE:
this->width = (Int32)LOWORD(lParam);
this->height = (Int32)HIWORD(lParam);
break;

case WM_SETTEXT:
this->title = wstring( reinterpret_cast<WCHAR_STR>(lParam) );
break;

case WM_DESTROY:
PostQuitMessage( 0x00 );
break;
}

return DefWindowProc( this->hWnd, msg, wParam, lParam );
}
[/source]

???

Now my text is changing correctly, but I just want to be sure that structuring my WndProc method like this is ok and isn't going to cause any problems for my class. The original version was returning 0x00 instead of the result of DefWindowProc.

[b]EDIT:[/b]

I assume that if I do it this way and I want to block Windows from getting a message then I can replace a break with a return. Edited by ATC
0

Share this post


Link to post
Share on other sites
That's what I spoke about in my first post. Always return DefWindowProc() for all messages, even the ones you process, except in the case where you know that you do NOT want DefWindowProc() to process the message, and that the value you are returning instead is meaningful to the system. DefWindowProc() does A LOT of things, and the less you interfere with it (the less messages you keep from it), the less problems you are likely to have. So yes, that structure of the message procedure is the natural one.
[quote]I assume that if I do it this way and I want to block Windows from getting a message then I can replace a break with a return.[/quote]
Yep, but again, see the documentation for the message in question to know what to return. Edited by Amr0
0

Share this post


Link to post
Share on other sites
[quote name='Amr0' timestamp='1350760045' post='4992233']
That's what I spoke about in my first post. Always return DefWindowProc() for all messages, even the ones you process, except in the case where you know that you do NOT want DefWindowProc() to process the message, and that the value you are returning instead is meaningful to the system. DefWindowProc() does A LOT of things, and the less you interfere with it (the less messages you keep from it), the less problems you are likely to have. So yes, that structure of the message procedure is the natural one.
[quote]I assume that if I do it this way and I want to block Windows from getting a message then I can replace a break with a return.[/quote]
Yep, but again, see the documentation for the message in question to know what to return.
[/quote]

Gotcha! Thanks a lot! :-)

I've got a nice general purpose Window class coming together now... now working on wiring up some events and such. When it's done I won't feel so bummed out every time I start a new Win32 or native DirectX project (from having to do all this crap over again). :P

Thanks again,

--ATC--
0

Share this post


Link to post
Share on other sites
CRAP! I cannot believe I missed that! You don't need to process WM_CREATE or WM_PAINT or most of the other messages, but you do need to return DefWindowProc().[img]http://public.gamedev.net//public/style_emoticons/default/sleep.png[/img]
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0