2006/7/27, Micha Nelissen <[EMAIL PROTECTED]>:
Alexandre Leclerc wrote:
> 2006/7/27, Alexandre Leclerc <[EMAIL PROTECTED]>:
>> Oh yeah! Thank guys! This is exactly what I was looking for and it's
>> working great!
>
> Ok, if i queue a call and close a form I'll get a problem because the
> last message is executed after teh form is no more... Is there a call
> to process these messages first before exiting? (I tried
> ProcessMessage in the OnClose event but it did nothing. The procedure
> gets called too late. Unless there is another way of checking to avoid
> problems?
No, all messages are processed before calling methods in the queue. Why
do you need to have your method called earlier ?
I just saw that ProcessMessages is processing the queue after the
messages. Now I understand better my proble,: a control is placing a
call in the queue when being destroyed; thus when the queue is
processed it will try to interract with a destroyed control.
Now, I can't remember that status/state property of a control to know
if it is in a destroy operation so that I would not add a call in the
queue.
--
Alexandre Leclerc
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
