Daklu wrote: That trick wouldn't work with my style because the event loop always dispatches messages to other loops that do the actual work, so the event queue doesn't get backed up. If you're running a SQL query in a UI loop, what happens if your database is slow or unresponsive? |
It's SQLite and very fast. Probably wouldn't do it this way if the potential delay were too high. But if the update was a second, say, then the User would see one update a second, always reflecting where the control was a second ago (in practise I've seen no noticable delay yet).
BTW, an alternate trick, more coding but more flexible and would work for your style, is to have the final loop use flags to indicate what needs updating, and do any actual updating in the timeout case. Use a shift register coming from a "use default if unwired" case-structure output; the timeout case would supply a "-1" timeout, while the other cases would use the default zero timeout. That way a burst of events can be quickly analysed to see what needs updating, but the updating itself is only done at the end (thus ignoring multiple events that all require the same update).
