I'm using SendInput instead of keybd_event and mouse_event, but I encounter problems when the current desktop switches to the Winlogon screen. Since I already knew VNC allows keyboard and mouse movements in this state, I decided to look through the source to look for a solution.

While sending inputs to a regular desktop, no problems occur. From what I can tell, vncClientThread::run switches to the current desktop available and sends its input from there; however, it's not clear if running this as a separate thread is what allows the keyboard and mouse events to be properly interpreted. Does the following code allow a separately running thread to send inputs while in the Winlogon desktop (screen you arrive at after pressing ctrl-alt-del)?

if (!InputDesktopSelected())
        if (!SelectDesktop(NULL))

If not, what does? I'd appreciate any input on this, and perhaps an explanation on when vncClientThread::run is actually called. I'm running my application as a service, if that comes up. Thanks for any help!


Kind regards,


John-Michael Carolan
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to