> -----Original Message----- > From: Keith Hall [mailto:K.Hall@;servicepower.com] > > It happens when you press capslock on the host machine, instead of > 'activating capslock' on the remote machine as well, it just > seems to 'hold > shift down'... pressing shift (both) will release the 'hold' > and problems will disappear. > > I think a quick dirty fix would be for VNC developers to put > a shift up event after capslock is pressed?
That would be verry dirty, not so fast and an anoying bug instead of a fix. The caps-lock key is a total different key than the shift key. I have never seen the captial variants of 1234567890: with caps-lock, I get 1234567890, with shift I get !@#$%^&*() . I've had troubles with a VT320 terminal (the hardware) that has an option to define a lock key as either a caps-lock or a shift-lock. This shift-lock setting (sometimes caused by bad terminal settings in the software) is a real pain in the ass. > > Or is there nothing sent when capslock is pressed except a > 'hold shift down' event? The normal key events should be send: the caps-lock-key-down and caps-lock-key-up, according normal keyboard actions. After all, the vncviewer does not know the system at the other end. CBee _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
