[FreeNX-kNX] caps-lock toggle?
chris at ccburton.com
chris at ccburton.com
Fri Feb 28 11:15:44 UTC 2014
freenx-knx-bounces at kde.org wrote on 26/02/2014 18:46:09:
> Somehow my caps-lock state got out of sync with an NX/freenx session.
Yup happens all the time,
also with alt tightvn-vnc ( which has a nice button to put it back)
(
I always end up with alt depressed after alt-tabb-ing round to a session
even tho I released alt :("
I've seen it with just about every remote etc
> I run multiple simultaneous NX sessions, sometimes mixed with VNC,
> vmware, x2go and synergy from the same desktop
busy
> so I'm not too surprised at something getting the keyboard state wrong.
> But, is there any way to fix it short of terminating that session and
> everything running in it? A suspend/reconnect still comes back with
> the state reversed from the actual keyboard - and from what any of the
> other apps on the local desktop see.
Hmm well sort of there is.
Method No.1 is to have a script on the NX server to switch it
independently of the client . . .
You can probably download one, I haven't felt the need yet.
Method No. 2 - catch the right moment to switch the client caps lock
The two ends start off a connection with the
then current state of num-lock shift-lock etc
then
monitor key presses
so
sometimes a key press gets missed if occurs at the wrong time
so
if you hit connect in the nxclient with caps lock
then
UN-CAPS LOCK just as the X session is starting, (after authentication)
you can get the session to miss the key-press.
But you'll need to try a few times to get to know when to do it.
NOTES
I've seen a few instances with the OpenNX client against Opensuse 12.2
where
I couldn't reconnect at all if there was a mismatch
i.e I hit caps lock by mistake in the session then disconnected
(just tried it again and got
Loop: PANIC! Can't identify NX port in string ':'.
Error: Can't identify NX port in string ':'.
followed by an actual re-connect, but with the WP top menu fonts
all messed up.
BUT
I wouldn't say that 12.2 was a typical distro version tho
and
I've slightly modded my OpenNX too
but I can't be bothered going through the source with
OpenNX in its current state)
A good fix is to disable caps lock which is mostly useless,
if not most useless.
(I guess that 99%+ of caps lock use is by accident
With me it's 100%
( except when testing caps lock issues))
see
http://capsoff.org
but of course
that doesn't solve alt and ctrl issues
>
> --
> Les Mikesell
> lesmikesell at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20140228/be0c678f/attachment.html>
More information about the FreeNX-kNX
mailing list