cursor position
in [Device Drivers]
|
Prev: WinUSB and xp3 DTM tests
Next: Delay in DPC : CRASH
From: Ivan Brugiolo [MSFT] on 4 Feb 2010 15:29 XPDM display drivers are Session-Space drivers. Only the XPDM miniport is a System-Space driver, but, that is not cursor aware by any standardized means. For WDDM, only the session bound to the glass terminal can use the WDDM stack to drive a primary attached to the desktop, so the problem is somewhat solved, because you can draw a cursor only to a scanout surface. -- -- 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 "Aram Hăvărneanu" <aram.h(a)mgk.ro> wrote in message news:23B29449-675F-4E45-A38F-2CA407B9E8DC(a)microsoft.com... > > "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 |