>The problem is that the G4 is so fast that before I can release the mouse
>button
>after having closed the dialog, it is reading another mouse click and
>passing it
>on. By doing a FlushEvents, it reads the first one, gets rid of the Dialog and
>flushes the rest of them away, so another mouse click is not read - causing
>something else to happen before the user wishes it to happen.
>
>Sorry, I brought this whole subject up. My sole purpose was to "alert" you
>guys to
>the likelihood that the same may happen to you and you might be aware of
>it. There
>are a limit number of situatins in which it could cause a problem, but it
>could
>cause something to happen that caused you to scratch your hears/beards a few
>times.
>
>Joe Wilkins

Joe:

Okay, place a DELAY after the event.

tedd

_______________________________________________________
http://sperling.com/