Tom1 Posted April 1, 2013 Author Share Posted April 1, 2013 You're stopping the thread from running ever again unless you're restarting it constantly .. lol No I am not? The thread processes at a 600ms tick, that "return" statement doesn't stop the thread from processing. Link to comment Share on other sites More sharing options...
Blutengel Posted April 2, 2013 Share Posted April 2, 2013 Really couldn't think of anything else to call itI find this name to be quite descreptive for what it does. Other names such as "CycleScheduler" might give false impressions that it only calls every so often, like a ScheduledExecutorService. Link to comment Share on other sites More sharing options...
Bythex Posted April 2, 2013 Share Posted April 2, 2013 No I am not? The thread processes at a 600ms tick, that "return" statement doesn't stop the thread from processing. return stops the whole loop which stops the thread, if you want me to take a picture of me testing this than I could go ahead. Link to comment Share on other sites More sharing options...
Bot Posted April 2, 2013 Share Posted April 2, 2013 So this is basically events with an extra integer to tell which cycle it is on. Thanks for your input Thomas however I disagree with what you're passing this as. Link to comment Share on other sites More sharing options...
Vastico Posted April 2, 2013 Share Posted April 2, 2013 Err what? http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/Phaser.html 2 Link to comment Share on other sites More sharing options...
Guest mainniam Posted April 3, 2013 Share Posted April 3, 2013 this is already implemented in the standard library. 1 Link to comment Share on other sites More sharing options...
