Re: [opensuse] tightvnc version
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]
Re: [opensuse] tightvnc version
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]
Re: [opensuse] tightvnc version
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. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] tightvnc version
On Sunday 03 June 2007 01:27, M Harris wrote: > I have a minor concern with the way the numeric keypad is handled, and I am > wondering whether this has already been addressed, or if I need to open a > bug report. I did some searching but did not find what I was looking for. > > In version 1.2.9 the numeric keypad is not being handled properly when the > numlock is on. From my vncviewer client I am accessing my remote kde > desktop and running (from within a konsole) the xev tool. This displays the > x events (keypresses and keyreleases) plus the associated keysyms. With the > numlock off the keypad works as I would expect it to. The 7 key is keysym > KP_Home, the 8 key is KP_Up, etc. Each key receives ONE keypress event, > and ONE keyrelease event. However, when the numlock is on then the > behavior is not expected which causes different kinds of problems depending > which app is needing the keypad. With numlock on the 7 key recieves [ in > this order ] : keypressshift_L > keypressKP_7 > keyrelease shift_L > keyrelease KP_Home > [ this is not correct behavior, even though it does work > for some things ] > The 8 key press with numlock on gives: > keypressshift_L > keypressKP_8 > keyrelease shift_L > keyrelease KP_Up > [again, not correct and very strange behavior in some apps] > > The shift meta keys should not be used at all--- although the technique > would work for the most part if the keyreleases were in the correct order. > Here is what happens in kcalc --- the 8 key activates the * key > [multiplication key] why?-- because the 8 is being interpretted as an "8" > with the shift_L key down... "*". > > Using the shift_L technique vncviewer should be sending the keyrelease > shift_L *last*. However, even so, it will not work in KCalc because the 8 > key will still be interpretted as an * . > > What should be happening is this: > keypressNum_Lock > keyrelease Num_lock > keypressKP_8 > keyrelease KP_8 > > So, I would like to know is this a bug? If so, has it been fixed in 1.3.x > (I have downloaded the tarball but have not installed it as yet)? Is there > a work-around in the current version, or is there something I am missing > here? > > > > 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! > UmThis a way off the wall suggestion. I remember a thread a while ago about the left and right shift keys being mapped differently. Maybe ?? Bob S -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] tightvnc version
On Saturday 02 June 2007 06:59, Joseph Loo wrote: > I get a multiplication when doing it. I do not think it is tightvnc that is > doing it because, if you open a standard xterm, it comes out as 8. Yes, that is my result also... that is why I used xev... because it will tell me exactly which keysyms are being sent to KDE and being interpretted by KCalc... this is the update I sent to the tightvnc people: I am using tightvnc 1.2.9 which shipped with openSUSE 10.0. I have several headless application servers serving shared kde desktops across ssh tunnels with the vncviewer also running as the client on openSUSE 10.0. This setup is working great, and I want to thank the team who is making GPL tightvnc possible. I have a minor concern with the way the numeric keypad is handled, and I am wondering whether this has already been addressed, or if I need to open a bug report. I did some searching but did not find what I was looking for. In version 1.2.9 the numeric keypad is not being handled properly when the numlock is on. From my vncviewer client I am accessing my remote kde desktop and running (from within a konsole) the xev tool. This displays the x events (keypresses and keyreleases) plus the associated keysyms. With the numlock off the keypad works as I would expect it to. The 7 key is keysym KP_Home, the 8 key is KP_Up, etc. Each key receives ONE keypress event, and ONE keyrelease event. However, when the numlock is on then the behavior is not expected which causes different kinds of problems depending which app is needing the keypad. With numlock on the 7 key recieves [ in this order ] : keypressshift_L keypressKP_7 keyrelease shift_L keyrelease KP_Home [ this is not correct behavior, even though it does work for some things ] The 8 key press with numlock on gives: keypressshift_L keypressKP_8 keyrelease shift_L keyrelease KP_Up [again, not correct and very strange behavior in some apps] The shift meta keys should not be used at all--- although the technique would work for the most part if the keyreleases were in the correct order. Here is what happens in kcalc --- the 8 key activates the * key [multiplication key] why?-- because the 8 is being interpretted as an "8" with the shift_L key down... "*". Using the shift_L technique vncviewer should be sending the keyrelease shift_L *last*. However, even so, it will not work in KCalc because the 8 key will still be interpretted as an * . What should be happening is this: keypressNum_Lock keyrelease Num_lock keypressKP_8 keyrelease KP_8 So, I would like to know is this a bug? If so, has it been fixed in 1.3.x (I have downloaded the tarball but have not installed it as yet)? Is there a work-around in the current version, or is there something I am missing here? 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. :-| -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] tightvnc version
M Harris wrote: > On Friday 01 June 2007 22:39, Joseph Loo wrote: >> but under 10.2 I am using 1.2.9 > Thanks. I have run into a little small problem with the numeric keypad > (with > numlock on) and some apps like KCalc. 1.2.9 shipped with openSUSE 10.0. The > VNC people have release 1.3.9 (stable) ready--- I downloaded it tonight but > have not installed it as yet. > > I am noticing a little small problem with KCalc and the numeric > keypad... > would you try something for me on your 10.2 and let me know what happens > please ? > > vncviewer -via hostname hostname:1 [ what a great tip, thanks ] > > Then on your remote desk start KCalc from the suse menu. > > Then press the numlock on... and then enter an 8 key from the > keypad... > and tell me... does it enter an 8, or does it act like the X > [multiplication] key? > > I did some debugging on my system... with xev... but I spare you the > details > pending your feedback... but I don't think they are handling numlock > correctly. I am wanting to know whether its been fixed in the new release or > if I'm missing something here... thanks again. > > I get a multiplication when doing it. I do not think it is tightvnc that is doing it because, if you open a standard xterm, it comes out as 8. -- Joseph Loo [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] tightvnc version
On Friday 01 June 2007 22:39, Joseph Loo wrote: > but under 10.2 I am using 1.2.9 Thanks. I have run into a little small problem with the numeric keypad (with numlock on) and some apps like KCalc. 1.2.9 shipped with openSUSE 10.0. The VNC people have release 1.3.9 (stable) ready--- I downloaded it tonight but have not installed it as yet. I am noticing a little small problem with KCalc and the numeric keypad... would you try something for me on your 10.2 and let me know what happens please ? vncviewer -via hostname hostname:1 [ what a great tip, thanks ] Then on your remote desk start KCalc from the suse menu. Then press the numlock on... and then enter an 8 key from the keypad... and tell me... does it enter an 8, or does it act like the X [multiplication] key? I did some debugging on my system... with xev... but I spare you the details pending your feedback... but I don't think they are handling numlock correctly. I am wanting to know whether its been fixed in the new release or if I'm missing something here... thanks again. -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] tightvnc version
M Harris wrote: > Which version of tightvnc shipped with 10.2? > > I am not sure which version was shipped, but under 10.2 I am using 1.2.9 -- Joseph Loo [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] tightvnc version
Which version of tightvnc shipped with 10.2? -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
