Hi!
No, a timer is a control that works only if the OS yields time to it.
DoEvents() - at least if it follows the VB 6 model - is more like a
systemwide .Refresh() call. In fact, you could put a method, Refresh(),
in your App subclass, and call DoEvents() from there. Then call
App.Refresh() from within a tight loop, and it'll (effectively) yield
time back to the OS so that it can handle controls that are waiting to
be updated, etc... You could, of course, just call DoEvents() in the
loop, but by centralizing the control, you could also call .Refresh()
on any custom controls from within App.Refresh() as well.
On Friday, August 29, 2003, at 11:31 PM, Lars Jensen wrote:
[New] [All] Application: Added a new method called DoEvents to allow
you to yield time back to REALbasic in tight loops.
This sounds like I can get rid of a bunch of timers, if their only
purpose
was to allow the UI to receive events while I was doing stuff. Is that
right? If so, this will simplify a lot of code.
lj
---
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>
---
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>
|