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

Psepha

Of Threads and Things

6 posts in this topic

Why not just use the WM_CLOSE message, and delete your stuff there?

------------------
Dance with me......

0

Share this post


Link to post
Share on other sites
Umm - The WM_CLOSE message is received on the thread that controls the window - not the background task that controls the sound capture and network send processing. I guess the questio really is how do you close down a thread cleanly when it may need to interact with another thread that may be closing
0

Share this post


Link to post
Share on other sites
I assume that Function() is running in another thread. If you close down the app while the other thread is in its "Do something" bit then the "delete[] Buffer" will never be reached. This is because when the main process dies, all its threads die immediately, before they can cleanup.

One simple thing you can do set a global flag when you want all your extra threads to terminate. The threads should ocasionally look at this flag and exit their "Do something" bit when it is set.

To stop the main process from terminating before all the threads have cleaned up, you can use the WaitForSingleObject or WaitForMultipleObjects API functions. Just pass them the handle of your thread or threads and they will delay your main process until all the threads have exited.

Something like this:

/*** Main process ***/

bool g_finished = false;

// Called just before main process dies.
void OnQuit()
{
g_finished = true;
WaitForSingleObject(h_thread, INFINITE);
}


/*** Extra thread ***/

void Function()
{
Buffer = new char[100];
DoSomething();
delete[] Buffer;
}

void DoSomething()
{
while (!g_finished)
{
// do stuff
}
}

0

Share this post


Link to post
Share on other sites
If your window is aware of the thread you are worried about, you can ask the thread if it is finished during the WM_CLOSE message, and wait for it there, which is what I usually do.

-fel

0

Share this post


Link to post
Share on other sites
Bascially, you combine the above two tactics. In the WM_CLOSE message, a global variable is set when threads are to clean up, then you WaitForMultipleObjects() for your threads to finish up, see the flag and quit, then you quit the main thread. Its not particularly hard or complex.

- Splat

0

Share this post


Link to post
Share on other sites
Thanks people - Alastair - Looks like the solution I'm gonna try - Seen it before but never used it

Thanks All

Psepha

0

Share this post


Link to post
Share on other sites
Hi all again.
A windows general coding question this time. Am just completing an network telephone program (game talkover type thing)and all appears to be going to plan (works) except where you close down the application. As you can hit the window close button at any time you can end up with resource leaks.....
eg
Function()
{
Buffer = new char[100];
Do something for a bit...
delete[] Buffer;
}

If you close the application whilst performing the Do something for a bit... code the delete[] function is not called. Hmm...I am assuming this is partly because the sound capture and network transmission side of the app runs on another thread....Hmmm...
Any ideas? Should I create some sort of global flag 'DontKillTheAppYetCosImBusy' type thing? Seems a bit messy.......

Psepha

0

Share this post


Link to post
Share on other sites