Good research Christophe! CC> Holding the mouse button creates an event which is queued for handling. CC> When the new screen is composed, a 'feel+engage event is triggered, for CC> the chronometer. When rebol starts this event, some mouse-event CC> remaining from the previous screen was not completely handled and causes CC> the crash.
CC> What we think to do: CC> Before the new screen is composed and displayed, first "flush" the event CC> queue for cleaning the old mouse event that remains. Maybe a View guru will have some good advice, if you don't want to change your app too much. If a larger change is acceptable, I'd handle events with an FSM (Finite State Machine). Doing it that way puts you in control of when events are processed, so you can choose whether to hide the screen on a timer interval, or decide if you need to wait because you're in a "pending" state, processing another event. -- Gregg -- To unsubscribe from the list, just send an email to lists at rebol.com with unsubscribe as the subject.
