On 6/9/04 9:44 PM, K wrote:
This is not something that easily use the send in time construct. I do not wish to waste the run-time a send in WAG requires. What is the approiate construct to use so that several very intense repeat loops will get equal time? I have been using wait for messages which did not function as I would have expected. It seems that wait for messages only allow "new" habdlers to proceed nut does not yeild control to a handler already running a repeat construct. Maybe this is a question I should ask of the RR support. Any ideas?
Kevin
NOTE: Might there be a doEvents type construct which would allow 2 routines in tight loops to execute?
Unfortunately there isn't a construct like that. RR isn't multi-threaded, so your only option is to fake it using send in time. There isn't usually much runtime impact with this method and you gain a lot of control.
-- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
