Y
Y.Aykut ERGÝN
Hi,
First of all I really don't know where to post this problem,
excuse me and please direct me to the right newsgroup.
We develope multiprocessing application on windows 2000 and XP os for the
mentioned project.
We use Borland C++ Builder 6.0.
As a summary our problem:
Let's suppose we have multi processes running.( initialization and creation
of processes have no problem)
processA window visible enabled.
processB window visible disabled.
1.The active processA sends a WM_CUSTOMER message to an other processB.
2.processA window visible disabled.
3.When processB gets the message, creates and show the form.
4.FORM SEVERALLY OPENS INACTIVE
then we try some scenorias to correct this problem but we can't achieve to
handle this problem.
Scenarios we tried shown below;
1.processA sends first WM_CUSTOMER and then WM_SETFOCUS messages to
processB, but form still opens inactive.
2.processA sends WM_CUSTOMER and then when processB receives theWM_CUSTOMER
message, it sends WM_SETFOCUS to itself but form still opens inactive.
3.processA sends first WM_CUSTOMER and then WM_ACTIVATEAPP messages to
processB, but form still opens inactive.
4.processA sends WM_CUSTOMER and then when processB receives theWM_CUSTOMER
message, it sends WM_ACTIVATEAPP to itself but form still opens inactive.
5.processA sends first WM_CUSTOMER and then WM_ACTIVATE messages to
processB, but form still opens inactive.
6.processA sends WM_CUSTOMER and then when processB receives theWM_CUSTOMER
message, it sends WM_ACTIVATE to itself but form still opens inactive.
Any help is greatly appreciated.
Best regards,.
Aykut ERGÝN
Universal MSDN Member
First of all I really don't know where to post this problem,
excuse me and please direct me to the right newsgroup.
We develope multiprocessing application on windows 2000 and XP os for the
mentioned project.
We use Borland C++ Builder 6.0.
As a summary our problem:
Let's suppose we have multi processes running.( initialization and creation
of processes have no problem)
processA window visible enabled.
processB window visible disabled.
1.The active processA sends a WM_CUSTOMER message to an other processB.
2.processA window visible disabled.
3.When processB gets the message, creates and show the form.
4.FORM SEVERALLY OPENS INACTIVE
then we try some scenorias to correct this problem but we can't achieve to
handle this problem.
Scenarios we tried shown below;
1.processA sends first WM_CUSTOMER and then WM_SETFOCUS messages to
processB, but form still opens inactive.
2.processA sends WM_CUSTOMER and then when processB receives theWM_CUSTOMER
message, it sends WM_SETFOCUS to itself but form still opens inactive.
3.processA sends first WM_CUSTOMER and then WM_ACTIVATEAPP messages to
processB, but form still opens inactive.
4.processA sends WM_CUSTOMER and then when processB receives theWM_CUSTOMER
message, it sends WM_ACTIVATEAPP to itself but form still opens inactive.
5.processA sends first WM_CUSTOMER and then WM_ACTIVATE messages to
processB, but form still opens inactive.
6.processA sends WM_CUSTOMER and then when processB receives theWM_CUSTOMER
message, it sends WM_ACTIVATE to itself but form still opens inactive.
Any help is greatly appreciated.
Best regards,.
Aykut ERGÝN
Universal MSDN Member