🚀 go-pugleaf

"Damian Vilchis" <damian@ininin.com.mx> wrote in message
news:3fc28a38@newsgroups.borland.com...

> Yes, but once finished the external application the
> messages in the queue are processed.

No, they are not.  The message queue is not touched in any way unless you
call ProcessMessages(), or a component calls ProcessMessages(), or you let
execution flow back to the message queue itself normally.

> Again the same, the form is painted inmediately no problem, but if
> the user pressed a button in the calling form while the external
> application is runningon this message is processed when the application
> is finished and not discarted like in the modal case.

Modal forms run a separate message queue while they are visible, processing
all of the messages in the message queue until the form is closed.  If you
do not want there to be any pending messages after you return from the
external application, then you'll just have to pump the queue manually to
clear out and discard all pending messages.  Which is not a good thing to
do.

> I solve the problem simply disabling the calling form before the
> external application is launched, and enabling once the application is
> finished.

That is fine.


Gambit