🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:
> "Damian Vilchis" <damian@ininin.com.mx> wrote in message
> news:3fc24ad9$1@newsgroups.borland.com...
> 
> 
>>The problem with both aproaches is that not only the paint message
>>is processed. If I use ProcessMessages, any message is processed
>>and this eliminate the Modal behavior.
> 
> 
> If you use Update(), the form will be repainted without processing other
> messages.

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

> 
> 
>>Update work a little better, only repaint the form, but the
>>messages are enqueued
> 
> 
> No, they are not.  TWinControl::Update() calls the Win32 API function
> UpdateWindow(), which sends the WM_PAINT message directly to the window
> procedure without using the message queue at all.  Thus the form is
> repainted immediately.
> 

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.

> 
>>tha calling application must be able to paint itself but not anymore.
> 
> 
> That is what Update() is for.
> 
> 
> Gambit
> 

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

Thanks.