aboutsummaryrefslogtreecommitdiffstats
path: root/unix/xserver
diff options
context:
space:
mode:
authorPierre Ossman <ossman@cendio.se>2018-09-21 12:30:36 +0200
committerPierre Ossman <ossman@cendio.se>2018-09-21 12:30:36 +0200
commit764c60904b2be6d0e486f80eb9d541b7c331c4fc (patch)
treeb63f71acb9d8a41c7315fb784f1ae7830f864757 /unix/xserver
parent6d0a5a267b5b4c45a97f3e60db7d28785c5ec1ee (diff)
downloadtigervnc-764c60904b2be6d0e486f80eb9d541b7c331c4fc.tar.gz
tigervnc-764c60904b2be6d0e486f80eb9d541b7c331c4fc.zip
Update NumLock comment now that we have sync
Diffstat (limited to 'unix/xserver')
-rw-r--r--unix/xserver/hw/vnc/Input.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/unix/xserver/hw/vnc/Input.c b/unix/xserver/hw/vnc/Input.c
index 5c458f5d..228b382d 100644
--- a/unix/xserver/hw/vnc/Input.c
+++ b/unix/xserver/hw/vnc/Input.c
@@ -537,9 +537,9 @@ static void vncKeysymKeyboardEvent(KeySym keysym, int down)
* get confused when we do a fake shift to get the same effect
* that having NumLock active would produce.
*
- * Until we have proper NumLock synchronisation (so we can
- * avoid faking shift), we try to avoid the fake shifts if we
- * can use an alternative keysym.
+ * Not all clients have proper NumLock synchronisation (so we
+ * can avoid faking shift) so we try to avoid the fake shifts
+ * if we can use an alternative keysym.
*/
if (((state & ShiftMask) != (new_state & ShiftMask)) &&
vncGetAvoidShiftNumLock() && vncIsAffectedByNumLock(keycode)) {