RE: FindWindow warning

2000-11-11 Thread Chet Murphy


 At 11:40 PM 11/10/00 +0100, you wrote:
 Is the following FIXME correct (and the comment as well)?
 snip fixme about FindWindow not working for another process

 That's a following of the address space separation. Although the Wine processes
 are separated, the windows handles are still generated by each Wine process
 through a local mechanism based on memory allocation. The Wine server does not
 generate them, and as such these handles have no meaning for another process.

 For example, it can happen that 2 windows of different processes have the same 
handle.
 So it does not make sense to do a FindWindow for a window in another process
 in current Wine.
 The main problem for fixing that is probably to not having performance going
 down the drain :-)

Then it sounds like the problem is not just with FindWindow. One important use window 
handles is
when using WM_COPYDATA to send data from one process to another. I use WM_COPYDATA to 
send data
between instances of my applications. I also use WM_COPYDATA when using a custom hook 
dll that will
be loaded by another process so that the custom hook dll and my application can 
establish
interprocess communication (in this case I pass my application's window handle to the 
dll as part of
the command line). If window handles are local to the process then how can WM_COPYDATA 
work for
interprocess communication?

Chet Murphy
Modelworks Software
[EMAIL PROTECTED]
http://www.modelworks.com
voice: 425 488 5686
fax: 253 830 7802





FindWindow warning

2000-11-10 Thread Joerg Mayer

Is the following FIXME correct (and the comment as well)?

 Ciao
   Jörg
-- 
Joerg Mayer  [EMAIL PROTECTED]
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.


Index: wine/windows/win.c
===
RCS file: /home/wine/wine/windows/win.c,v
retrieving revision 1.104
diff -u -r1.104 win.c
--- wine/windows/win.c  2000/11/02 20:08:59 1.104
+++ wine/windows/win.c  2000/11/10 21:36:28
@@ -1576,6 +1576,10 @@
 }
 }
 retvalue = 0;
+/* In this case we need to check whether other processes
+   own a window with the given paramters on the Desktop,
+   but we don't, so let's at least warn about it */
+FIXME("Returning 0 without checking other processes\n");
 end:
 WIN_ReleaseWndPtr(pWnd);
 return retvalue;



Re: FindWindow warning

2000-11-10 Thread gerard patel

At 11:40 PM 11/10/00 +0100, you wrote:
Is the following FIXME correct (and the comment as well)?
snip fixme about FindWindow not working for another process

That's a following of the address space separation. Although the Wine processes
are separated, the windows handles are still generated by each Wine process
through a local mechanism based on memory allocation. The Wine server does not
generate them, and as such these handles have no meaning for another process.

For example, it can happen that 2 windows of different processes have the same handle.
So it does not make sense to do a FindWindow for a window in another process
in current Wine.
The main problem for fixing that is probably to not having performance going 
down the drain :-)

Gerard