cursor position
in [Device Drivers]
|
Prev: WinUSB and xp3 DTM tests
Next: Delay in DPC : CRASH
From: suhas on 3 Feb 2010 06:31 can we read the cursor position in the driver itself
From: Doron Holan [MSFT] on 3 Feb 2010 13:02 nope -- This posting is provided "AS IS" with no warranties, and confers no rights. "suhas" <suhas(a)discussions.microsoft.com> wrote in message news:5C368488-FC6B-4295-8830-892CF4803E21(a)microsoft.com... > can we read the cursor position in the driver itself
From: Ivan Brugiolo [MSFT] on 3 Feb 2010 17:47 It really depends. If you are in a display driver, and according to reported capability and system configuration, you may have a call to one of those WDDM - DxgkDdiSetPointerPosition XPDM - DrvMovePointer / DrvSetPointerShape. In any other environment, the information is not accessible. -- -- This posting is provided "AS IS" with no warranties, and confers no rights. Use of any included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm "suhas" <suhas(a)discussions.microsoft.com> wrote in message news:5C368488-FC6B-4295-8830-892CF4803E21(a)microsoft.com... > can we read the cursor position in the driver itself
From: Kerem Gümrükcü on 3 Feb 2010 19:55 >In any other environment, the information is not accessible. I dont understand: Why do people need the position of the mouse on the screen inside a driver??? This is something that you will need in user mode with user interfaces not inside a driver. If you want to restrict/set the pointer to something or somewhere, then you simply write a user mode app and leave that task to it,... Regards K. -- ----------------------- Beste Grüsse / Best regards / Votre bien devoue Kerem Gümrükcü Latest Project: http://www.pro-it-education.de/software/deviceremover Latest Open-Source Projects: http://entwicklung.junetz.de ----------------------- "Ivan Brugiolo [MSFT]" <ivanbrug(a)online.microsoft.com> schrieb im Newsbeitrag news:#EWBaLSpKHA.3748(a)TK2MSFTNGP02.phx.gbl... > It really depends. > If you are in a display driver, and according to reported capability > and system configuration, you may have a call to one of those > WDDM - DxgkDdiSetPointerPosition > XPDM - DrvMovePointer / DrvSetPointerShape. > In any other environment, the information is not accessible. > > -- > > -- > This posting is provided "AS IS" with no warranties, and confers no > rights. > Use of any included script samples are subject to the terms specified at > http://www.microsoft.com/info/cpyright.htm > > > "suhas" <suhas(a)discussions.microsoft.com> wrote in message > news:5C368488-FC6B-4295-8830-892CF4803E21(a)microsoft.com... >> can we read the cursor position in the driver itself >
From: Aram Hăvărneanu on 4 Feb 2010 06:00
"Ivan Brugiolo [MSFT]" <ivanbrug(a)online.microsoft.com> wrote in message news:#EWBaLSpKHA.3748(a)TK2MSFTNGP02.phx.gbl... > It really depends. > If you are in a display driver, and according to reported capability > and system configuration, you may have a call to one of those > WDDM - DxgkDdiSetPointerPosition > XPDM - DrvMovePointer / DrvSetPointerShape. > In any other environment, the information is not accessible. How does this work, isn't the cursor position a session thing? What cursor position would I get with that method? I must confess I know nothing about the relation between the video driver and RDP, but my psychic powers tell me that there is none. Thanks, -- Aram Hăvărneanu |