The hook driver capture the rectangles and points passed to the driver
drvbitblt and drvcopybits functions.
The destination rectangles are screen coordinates, source rectangles are
window coordinates.
Vnc needs only to know the place that changed (for bitblt is this ok)
But when you want to use "copyrect" you also need the source info, you
have to know the source rectangle
before you can copy him to the destination.
I'm still try to find a way to translate the window coordinates to
screen coordinates.
The hook driver pass a RECT for bitblt and a RECT and POINT for
copybits. But the POINT is the place on the
window that moves.
ex: notepad size 100x100
place:
left = 150
right =250
top = 300
bottom =400
The driver pass me something like 160,240,310,380 point 0,10
rectangle moved to 160,240,310,380 from 150,310
But the driver don't tell me that the app is notepad and so I don't know
the starting place (150=0,300=10)
-----------------------------------------
There exist a document from microsoft "Tracking window changes" but this
document is not clear for me.
http://msdn.microsoft.com/library/en-us/graphics/dpyddi_4zon.asp
Rudi
-----Original Message-----
From: James ''Wez'' Weatherall [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 05, 2001 12:17 PM
To: Rudi De Vos
Cc: VNC-LIST
Subject: Re: hook video driver
Rudi,
I noticed your mail to the VNC list regarding a hooking video
driver.
>From your mail, it sounds as though you have this on Windows 2000/NT.
Is
that correct?
You mentioned some confusion in tracking window changes. Can you
give
more detail as to why this confusion exists, and I'll make suggestions
if I
can.
Cheers,
---
James "Wez" Weatherall
"The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK - Tel : 343000
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------