Hi all,
Using D2007 under XPSP3.
Is there a way to execute a kind of ProcessMessages method to a specific thread?
Here is my problem:
1. From a main form, I post a message to display the status of a record.
2. Before the message to be intercepted, the main form loads another form (which has parent a groupbox located on the main, so let's call it "child form" while is it not since it is SDI app).
3. From the child form, I initialize the display of a stringgrid (that is, setup columns title and width)
4. Before to display data, I post another message from the child form to fill the stringgrid (since the sql query might be slow and I do not want the display to flicker)
5. From that point, I would like the first message (main form) to be processes and after that, process the second message (child form), but cannot figure it out...
In other words, the main form (main thread) brings back control only after ALL messages has been intercepted in the child form (child thread).
How to call something like MainForm.ProcessMessages (because Application.ProcessMessages stays within child form only)?
Thanks for help,
Rej Cloutier
Using D2007 under XPSP3.
Is there a way to execute a kind of ProcessMessages method to a specific thread?
Here is my problem:
1. From a main form, I post a message to display the status of a record.
2. Before the message to be intercepted, the main form loads another form (which has parent a groupbox located on the main, so let's call it "child form" while is it not since it is SDI app).
3. From the child form, I initialize the display of a stringgrid (that is, setup columns title and width)
4. Before to display data, I post another message from the child form to fill the stringgrid (since the sql query might be slow and I do not want the display to flicker)
5. From that point, I would like the first message (main form) to be processes and after that, process the second message (child form), but cannot figure it out...
In other words, the main form (main thread) brings back control only after ALL messages has been intercepted in the child form (child thread).
How to call something like MainForm.ProcessMessages (because Application.ProcessMessages stays within child form only)?
Thanks for help,
Rej Cloutier