|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