At 04:55 PM 10/10/2001 +0200, you wrote: .
Alexandre> Implemented inter-process FindWindow().
Shouldn't this avoid errors like these: err:win:WIN_FindWndPtr window 1002a belongs to other process err:win:WIN_FindWndPtr window 10021 belongs to other process err:win:WIN_FindWndPtr window 10029 belongs to other process
Handles of other process windows can be returned by FindWindow, yes.
But current Wine returns them also in enumeration functions, like EnumWindows. A functions like SetCursor, when trying to set the cursor for all desktop children, triggers this kind of message.
The error message shows that Wine development is not complete because some function fails between processes (in SetCursor case, it is X11DRV_get_whole_window), not necessarily a problem in FindWindow.
Try to lookup the origin for the handles : it is a problem only if the app get them from a FindWindow call.
Gerard
"Gerard" == Gerard Patel gerard.patel@nerim.net writes:
Gerard> At 04:55 PM 10/10/2001 +0200, you wrote: . Alexandre> Implemented inter-process FindWindow(). >> Shouldn't this avoid errors like these: err:win:WIN_FindWndPtr >> window 1002a belongs to other process err:win:WIN_FindWndPtr window >> 10021 belongs to other process err:win:WIN_FindWndPtr window 10029 >> belongs to other process
Gerard> Handles of other process windows can be returned by FindWindow, Gerard> yes.
Gerard> But current Wine returns them also in enumeration functions, Gerard> like EnumWindows. A functions like SetCursor, when trying to set Gerard> the cursor for all desktop children, triggers this kind of Gerard> message.
Gerard> The error message shows that Wine development is not complete Gerard> because some function fails between processes (in SetCursor Gerard> case, it is X11DRV_get_whole_window), not necessarily a problem Gerard> in FindWindow.
Gerard> Try to lookup the origin for the handles : it is a problem only Gerard> if the app get them from a FindWindow call.
No the application does a SendMessage
096ed3f8:Call user32.SendMessageA(ffffffff,0000c00c,00000000,00000000) ret=004141aa err:win:WIN_FindWndPtr window 1002a belongs to other process err:win:WIN_FindWndPtr window 10021 belongs to other process err:win:WIN_FindWndPtr window 10029 belongs to other process 096ed3f8:Ret user32.SendMessageA() retval=00000001 ret=004141aa 096ed3f8:Call user32.SendMessageA(ffffffff,0000c00d,00000000,00000000) ret=004141bc err:win:WIN_FindWndPtr window 1002a belongs to other process err:win:WIN_FindWndPtr window 10021 belongs to other process err:win:WIN_FindWndPtr window 10029 belongs to other process 096ed3f8:Ret user32.SendMessageA() retval=00000001 ret=004141bc
096ed3f8 is a process created with Winexec, so I expect it to be a sibling. Why isn't the WindowsFunction of at least that process called?
Bye
-
Gerard Patel -
Uwe Bonnes