On Thu, 21 Jul 2011, DRC wrote:
On 7/21/11 1:24 AM, Peter Åstrand wrote:There's a state at the server and a state at the client. When you say "numlock is pressed", I assume that you mean that numlock is active at the client side? This will typically produce keysyms such as KP_1, which will sent over VNC. But in the Xvnc session, numlock is typically still off. This approach is what I recommend. But having numlock active in the Xvnc session may cause strange effects such as the one you are describing.I guess the thing I'm curious about is: why did it work before on some platforms? Based on Robert's original message, I infer that it worked with, for instance, the TigerVNC 1.1 Viewer for Windows connecting to the TigerVNC 1.1 Server.
I am also wondering. Could it be that the version of Xorg that you have been using to build your binaries automatically starts up with numlock enabled on the server side? We are still building Xvnc binaries with XOrg server 1.5.3, and we are not seeing this.
Rgds, ---
Peter Åstrand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Linköping Phone: +46-13-21 46 00
------------------------------------------------------------------------------ 5 Ways to Improve & Secure Unified Communications Unified Communications promises greater efficiencies for business. UC can improve internal communications as well as offer faster, more efficient ways to interact with customers and streamline customer service. Learn more! http://www.accelacomm.com/jaw/sfnl/114/51426253/
_______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
