• 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.

Archived

This topic is now archived and is closed to further replies.

Fundy Glostna

Mysterious quitting problem...

7 posts in this topic

I just made a basic window shell application for about the tenth time (as practice). It doesn''t do anything right now except handle messages, but I''m having trouble quitting! Every time I quit the application (using the X close button), I get an error! I debugged and I got this unusual message: First-chance exception in bitmaps.exe: 0xC0000005: Access Violation. The program ''C:\WINDOWS\Start Menu\Geoff''s Stuff\C++\DirectDraw\bitmaps\Debug\bitmaps.exe'' has exited with code 0 (0x0). My WM_DESTROY code is simply PostQuitMessage(0); I have no idea what''s wrong; everything seems perfect!
0

Share this post


Link to post
Share on other sites
Just a guess, but maybe you should try PostQuitMessage(1);
0

Share this post


Link to post
Share on other sites
Well, maybe... but what''s the differences b-tween PostQuitMessage(0) and PostQuitMesage(1), what is it stands?

The road may be long, wind may be rough. But with a will at heart, all shall begone. ~savage chant
0

Share this post


Link to post
Share on other sites
Well, that parameter is the exit code, a value that can be queried by other applications when the application in question terminates. The value you pass will be assigned to the wParam member of the MSG structure used in your app''s message pump which you''re then supposed to use as the final return value in WinMain. Although I haven''t seen any definitive word on this, Microsoft''s sample code always uses 0 as the parameter to PostQuitMessage, so I''d say that it''s probably the right value to use.
0

Share this post


Link to post
Share on other sites
quote:
Original post by Fundy Glostna
I just made a basic window shell application for about the tenth time (as practice). It doesn''t do anything right now except handle messages, but I''m having trouble quitting! Every time I quit the application (using the X close button), I get an error!

I debugged and I got this unusual message:

First-chance exception in bitmaps.exe: 0xC0000005: Access Violation.
The program ''C:\WINDOWS\Start Menu\Geoff''s Stuff\C++\DirectDraw\bitmaps\Debug\bitmaps.exe'' has exited with code 0 (0x0).

My WM_DESTROY code is simply
PostQuitMessage(0);

I have no idea what''s wrong; everything seems perfect!


Hi,

Try sticking the call to PostQuitMessage() in an WM_CLOSE message handler. I had a problem similar to yours the other day where my app wouldn''t terminate properly when I clicked the close button (the app window would disappear but the app would still be listed as an active proces when you clicked Ctrl + Alt + Del). I don''t know why but using a WM_CLOSE handler instead of a WM_DESTROY handler fixed the problem.

case (WM_CLOSE):
{
PostQuitMessage(0);
return 0;
} break;




0

Share this post


Link to post
Share on other sites
I disagree. This is how it should be done:
    
...
case WM_CLOSE:
DestroyWindow(hwnd);
return 0;

case WM_DESTROY:
PostQuitMessage(0);
return 0;


I'll bet that your problem has nothing to do with your app's message pump but, rather, something that happens when it terminates. For instance, that you might be using some resource that had just been deallocated or some such thing. Sadly, the debugger won't help you much with this sort of error. My suggestion is to start commenting out portions of your code no having to do with the message pump. Eventually, you'll hit the problem.

Edited by - merlin9x9 on January 28, 2002 1:42:58 AM
0

Share this post


Link to post
Share on other sites
Well, I re-wrote the code in a fresh workspace and project, and it worked perfectly. The problem might have been external, but I may never know!
0

Share this post


Link to post
Share on other sites
Aha! I figured it out after all! I had created a direct draw interface and a primary surface with a backbuffer in that application. After the main loop breaked, I released the main direct draw interface pointer FIRST, before releasing the surfaces, and that''s what caused the error.

BEFORE (BAD):
  
if(lpdd) lpdd->Release();
if(lpddsPrimary) lpddsPrimary->Release();
if(lpddsBack) lpddsBack->Release();


AFTER (GOOD):
  
if(lpddsPrimary) lpddsPrimary->Release();
if(lpddsBack) lpddsBack->Release();
if(lpdd) lpdd->Release();
0

Share this post


Link to post
Share on other sites