1 VNC LED state Pseudo-encoding
2 =============================
7 This document describes the Pseudo-encoding of LED state for RFB which
8 is the protocol used in VNC as reference link below:
10 http://tigervnc.svn.sourceforge.net/viewvc/tigervnc/rfbproto/rfbproto.rst?content-type=text/plain
12 When accessing a guest by console through VNC, there might be mismatch
13 between the lock keys notification LED on the computer running the VNC
14 client session and the current status of the lock keys on the guest
17 To solve this problem it attempts to add LED state Pseudo-encoding
18 extension to VNC protocol to deal with setting LED state.
23 This Pseudo-encoding requested by client declares to server that it supports
24 LED state extensions to the protocol.
26 The Pseudo-encoding number for LED state defined as:
28 ======= ===============================================================
30 ======= ===============================================================
31 -261 'LED state Pseudo-encoding'
32 ======= ===============================================================
34 LED state Pseudo-encoding
35 --------------------------
37 The LED state Pseudo-encoding describes the encoding of LED state which
38 consists of 3 bits, from left to right each bit represents the Caps, Num,
39 and Scroll lock key respectively. '1' indicates that the LED should be
40 on and '0' should be off.
42 Some example encodings for it as following:
44 ======= ===============================================================
46 ======= ===============================================================
47 100 CapsLock is on, NumLock and ScrollLock are off
48 010 NumLock is on, CapsLock and ScrollLock are off
49 111 CapsLock, NumLock and ScrollLock are on
50 ======= ===============================================================