like pass, but without ending the handler

[Dick Kriesel]

On 2/28/07 3:27 PM, "J. Landman Gay" <jacque at hyperactivesw.com> wrote:

> The important part is the "wait <time> with messages", which allows user
> input to occur simultaneously. That will allow you to put in a "stop"
> button. But while "wait with messages" does allow the messages to
> happen, it does not allow them to be acted on. They will pile up in a
> queue until the loop is exited. Some of them, anyway. I think some were
> just lost.

Jacque, could you please clarify this?  What's the difference between
happening and being acted on?  If Rev loses messages, I'd like to
understand, so I don't write code that's likely to fail and that cannot be
debugged.  

-- Dick