Wednesday, 12. April 2006 05:28.Fixed a bug in sync. Committed revision 366 (although most tests fail because Inserting rows in a form (10.04.06) is not finished.
User code may call Session.status() to specify a status message. The status message is supposed to describe what the process is currently doing. New: user code can now also implement his own getStatus() method instead of calling status().
The Toolkit decides when (or whether at all) to call Session.getStatus() and how to use this status message. For example CaptureConsole never calls getStatus(). TtyConsole calls getStatus() not more then 10 times/second by default because it has new variables update_interval and last_updated to avoid flickering.