On Monday 04 June 2007 22:31, Joseph Loo wrote:
> 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.
Yes, my folks do this much of the time... in fact, much of the time
we're
just piping a konsole back (X11 protocol over ssh) and that works just fine.
> 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.
Yes, I agree... and normally we're not running KCalc at all... as you
might
have guessed I have been using VNC for some time before even noticing this
little annoyance. I just happened to pull up KCalc for some quick diddy and I
just happened to be on one of my tightvnc sessions--- and my keypad started
behaving most peculiar. rats.
Anyway, I followed the suggestions of the VNC people and tried forcing
the
numlock setting in kde on startup to "off". In fact, I experimented with
setting it both ways--- and no difference. Because of the technique they are
using in the old version 1.2.9 of emulating numlock "on" behavior for the
keypad by using a shift_L keysym with the KP_8 keysym the 8 key gets
interpretted in KCalc as a "*" multiplication key one way or the other. I
still have not installed the latest version of tightvnc... probably tomorrow
morning.
--
Kind regards,
M Harris <><
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
