Jump to content
Sign in to follow this  
  • entries
    23
  • comments
    31
  • views
    19946

Creepin' along

Sign in to follow this  
coderx75

361 views

I made a pretty stupid mistake. I'm pretty new at multi-threading... and it shows. I've divided up my application into separate parts to be threaded: physics, video, even the GUI (see previous entries). However, I put my input code in the main application. WTF? I've gone through all this trouble to keep input and GUI from from experiencing slow-downs but I put the input in the main application. What happens during system slow-downs? Reading the harddrive, for instance? GAH!

So, tonight I created a new thread and placed the input routines within it. I'm using a mediator to communicate with it. It actually helped the asynchronous GUI rendering by making it refresh smoothly. Go me. Anywho, I'm just cleaning up code this week and throwing down some comments like a good programmer should do. More later! (I know, the suspense is excruciating)
Sign in to follow this  


1 Comment


Recommended Comments

Multithreading does nothing but give me the willies, heh. And reading this does not make me feel any more comfortable about tackling them. :P

Hope you have better luck with it than I have in the past. :)

Share this comment


Link to comment

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
  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!