wine for two, please.
rddone at att.net
Tue Nov 1 21:19:40 CST 2005
I was going to wait til tomorrow to test this, but couldnt wait.
This works perfectly for my app and couldnt have came at a better time.
I just created a simple Win32 dispatcher program for each screen and sent
the window creation messages to the HWNDs from FindWindow instead of the
local app and it creates the dialogs on any screen I want. Joy Joy!!!!!
It worked out perfectly since the threads that create windows have to send
messages to the main loop for it to create them so that the dialogs dont
from close when the thread exits anyway.
It is refreshing that after I went through all the battles of getting
multihead display, gcc, and wine running on Solaris that FINALLY something
would work so simply.
Thanks again to the whole Wine crew that made this possible!!!
At 04:26 PM 11/1/2005, Rob D wrote:
>At 01:54 PM 11/1/2005, Marcus Meissner wrote:
>>Running two "wine foo.exe" will act as if on the same machine, including
>>interchange of windows messages if the apps do that.
>So I could create 2 wine apps that simply duplicate the window creation
>and message handling , and have them use FindWindow and the like to enable
>using SendMessage and such to synchronize the windows?
>If so, that would MUCH simpler than the method I had started formulating.
More information about the wine-devel