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

std::thread question

10 posts in this topic

I just started using threads and I am having a problem were an INT global variable that is modified by a CREATED detached thread does not has the value I expect it to have after the CREATED thread finishes, how do I know the CREATED thread finished? I change to TRUE a global variable at the end of the function the CREATED thread is running. So in the MAIN thread (not exactly in the MAIN function code but inside a function, inside another function called by the MAIN) I check if this bool is true, if it is then I read the INT value but it isn't what I want it to be.

 

What I want to know is where can I find good tutorials about what not to do when using global variables in threads.

Edited by lomateron
0

Share this post


Link to post
Share on other sites
Read the documentation, especially about std::thread::joinable instead of using something blindly. Especially in C++ 'just trying it out' is not a good plan of action. A lot of things appear to work and will then stop working at the most inconvenient time; maybe days, weeks or motnhs later.
1

Share this post


Link to post
Share on other sites

what is the best way for the MAIN thread to know when the CREATED thread finished?

I don't want to use join() because it blocks the execution of the MAIN thread. The MAIN thread is an infinite loop till I close the app

0

Share this post


Link to post
Share on other sites

I never used std thread, but doing a search on google for "std thread" should give you all the info you need, and i suggest you read a bit about them before starting using threads. I think what you need is this.

Edited by Vortez
0

Share this post


Link to post
Share on other sites

Since when does C++ have standardized threading? Aww man. I gotta try this out.

Since C++11, so not that long ago, really.

0

Share this post


Link to post
Share on other sites

I am using now std::async,

*I want to run fuction() async when I make a mouse click,

*I don't want to run function() if it is still running, like when I make lots of fast mouseclicks

*when function() finishes I want to run other code

 

this is the code:

 

#include <future>
#include <thread>
#include <chrono>

bool closeApp=false;
bool mouseClick=false;

std::future<void> futur;

void function()
{
     ...some code....
}

main()
{
      futur = std::async(std::launch::async, [] {int jil=3;}); //this code line is to just make futur...future_status...ready

      while(!closeApp)
      {
            if(mouseClick)
            {
                    //if I make lots of fast mouse clicks, this will prevent from running function()
                    if(futur.wait_for(std::chrono::milliseconds(0))==std::future_status::ready)
                    {
                              futur = std::async(function);
                    }
            }

            if(futur.wait_for(std::chrono::milliseconds(0))==std::future_status::ready)
            {
                    //here goes the code I want to do when I am sure function() is ready so 
                    ...
                    ...
                    ...
            }
      }
      return 0;
}

 

If I add a breakpoint at :

//here goes the code I want to do when I am sure function() is ready so  

the breakpoint will be reached only when function() takes little time to finish

 

do I need to use futur.get() if I want to run std::async(function) again?

0

Share this post


Link to post
Share on other sites

ooooopps I just found the code I have had an error, the code I have is very different from the code In my previous post, 

the error was that I checked if the async function() finished just one time after like 0.5 seconds, so if function took more than 0.5 seconds the code didn't make what I want

so I think the code of my previous post is correct, I will want someone to tell me if it is, I am just a starter

Edited by lomateron
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