|Post 16 made on Thursday March 20, 2008 at 15:26|
I tried that, but that's also was not really satisfactory... with fast rotation it makes too big jumps. this (updating 1/3 of the time) was kind of a best compromise. sure it can be tweaked further
|Post 17 made on Thursday March 20, 2008 at 20:36 |
Hopefully you did not take offense...
Just a pet peeve of mine. If I see code that has to use System.delay() or GUI.updateScreen(), it's usually a sign that the developer is a procedural programmer and either doesn't understand event-driven programming
doesn't want to use an event-based mechanism such as scheduleAfter() that allows something to be called (sending yourself a message) at a later time.
I try to avoid both of these methods at all costs as I do real-time, event-driven, multithreaded programming for a living and scheduleAfter() just comes natural to me.
Philips Pronto Addict/Beta Tester
Please read the following:
Unsolicited commercial advertisements are absolutely not permitted on this forum. Other private buy & sell messages should be posted to our Marketplace
. For information on how to advertise your service or product click here
. Remote Central reserves the right to remove or modify any post that is deemed inappropriate.