GetCursorPos behavior on Screen Lock, Screen Saver or RDP window minimization

GetCursorPos behavior on Screen Lock, Screen Saver or RDP window minimization

Post by Andre » Tue, 25 Nov 2008 21:28:42


Hi,

I have an application that does some UI actions on other applications
and GetCursorPos is one of the functions used for that. I found that
GetCursorPos fails with no specific error code in case if the screen
is locked (Win+L) or, if in RDP session, when the session window is
minimized.

I did some googling and performed an investigation and found that the
first case falls under secure desktop lock (this is described here
http://www.yqcomputer.com/
and here http://www.yqcomputer.com/

But still need better description for this (set of APIs that wouldn't
work, ways to bypass that limitation).
Does anyone know why this happens and where can the subject be studied
more deeply?

Thanks,
Andrey