Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 1
    My apologies for pulling the "accepted" status, as this answer does completely answer the question. However, I think the other response more specifically targeted the issue I was having. If these could be merged together, that would be the perfect answer! Thank you for your help, I really do appreciate the background you provided. Commented Dec 3, 2018 at 13:56
  • @bgregs The other answer covers the question implied by the title ("Is this a decent thread architecture for a game?"); this one answers the one actually asked in the body ("Is there any benefit one way or the other to having the user input captured in the main thread, or the child thread?"). This may be a sign that the question needs improvement. If your goal is getting your feet wet with concurrent programming, 85% of the other answer is what you worry about after you've mastered the base concepts. Whether or not this answer is the accepted one is no skin off my nose. Commented Dec 3, 2018 at 14:21