I've read through the Bugzilla comments now. My view is that:

* Apps should try to avoid distinguishing between Shift and CapsLock. I don't know the internals of Motif, but since this seems to be a problem limited to just the Motif toolkit (and not GTK+, QT etc), I think it looks like the Motif guys are doing something wrong.

Btw, https://bugzilla.redhat.com/show_bug.cgi?id=577187#c0 is inconsistent, since is says that the test case is pressing Ctrl+w, but the xev log shows the result from "A".


* Regarding apps such as NEdit, which needs to distinguish between Ctrl+v and Ctrl+Shift+v: Yes, this is a problem. It can be seen with rdesktop running inside a Xvnc session as well.


* As the x11vnc documentation points out, the -capslock option is very "hackish" and unreliable. I doubt it can be implemented with Xvnc good enough to be of any use.


Besides the problem with Shift vs CapsLock, there's also the problem with NumLock. For example, some Windows applications wants to look at the NumLock state. rdesktop by default leaves it disabled. It can be enabled with the -N option, but this obviously doesn't work with Xvnc.

I believe a complete solution to these problems would require that we introduce some "lock sync scheme" extension (or convention) to the RFB protocol. It won't be easy. We would need to cover Scroll Lock, and perhaps other locks as well. This is actually on our TODO list, but with low priority. After all, the CapsLock is seldom used nowadays.

Best regards,
Peter Åstrand


On Tue, 30 Mar 2010, Adam Tkac wrote:

Hello all,

I got report in Red Hat bugzilla that CapsLock emulation breaks some
toolkits (https://bugzilla.redhat.com/show_bug.cgi?id=577187).

Basically some toolkits check which keys are pressed and behave
differently when you press, for example, CapsLock + a + CapsLock and
when you press Shift + a + Shift. Currently we ignore CapsLock press
as written in RFB protocol but as written in
https://bugzilla.redhat.com/show_bug.cgi?id=577187#c5, x11vnc has
option which deals with CapsLock press as "expected" so it is
simply "pressed" on server side.

What do you think about that -capslock option? I know it is not nice
but I don't know about better solution of this problem.

Comments are welcomed.

Regards, Adam

--
Adam Tkac, Red Hat, Inc.

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel



---
Peter Åstrand           ThinLinc Chief Developer
Cendio AB               http://www.cendio.com
Wallenbergs gata 4
583 30 Linköping        Phone: +46-13-21 46 00
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Reply via email to