Bob S wrote: > On Sunday 03 June 2007 01:27, M Harris wrote: > >> The tightvnc folks say to install the 1.3.9 version... which I *have* >> downloaded, but which I have not installed as yet. They tell me that the >> old version numlock state was the state of the Server PC instead of the >> Client PC. When the client pushes numlock the numlock comes on at the >> client but stays off at the server<?>. Yikes. I am playing with that >> now... but have not confirmed that that is my problem. I still think its a >> bug in vncviewer. Different apps give different results depending on >> whether the keyreleases are valid symbols for the app! >> >> I'll keep you posted. :-| >> > Please disregard my last stupid suggestion. I did not understand your post. > > Sorry. > > Bob S. You have to be careful what terminology you are using. If it is using the X-11 terminology, the server is your machine and the client is the machine hosting the program.
Another question, I have, is why not just run the program as an X-11 server. For instance, if you run kcalc, do ssh -X hostname kcalc kcalc will now open in your machine but execute the program on host name. In general, I run tightvnc only when I need to see what actually is happening on the screen e.g., watch the user work the compuer or to have programs constantly running. In my case, my host machine is running bit torrent and I want to control the operation of the bit torrent client remotle. My hostname compuer does not have any keyboard or monitor. -- Joseph Loo [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
