Re: xmodmap patch to vnc 3.3.3 (interesting discoveries!)

2002-03-23 Thread Marius Kotsbak
t; 128 0x00e5 (aring) 0x00c5 (Aring) 0x00?? (somekey) > will work but the reverse: > 127 0x00e5 (aring) 0x00c5 (Aring) 0x00?? (somekey) > 128 0x0073 (s) 0x0053 (S) 0x00e5 (aring) > will not, since the server will find entry #127 first. > > On March 22, 2002 12:21 pm, you wrote: &

Re: xmodmap patch to vnc 3.3.3 (interesting discoveries!)

2002-03-22 Thread Marius Kotsbak
(this might have been sent before, but I send it again as I didn't receive my post) I have attatched my findings, like you requested and more. On Thu, 2002-03-21 at 17:30, Grant McDorman wrote: > According to Marius Kotsbak: > > I tried your trick, but it didn't have any

Re: xmodmap patch to vnc 3.3.3

2002-03-21 Thread Marius Kotsbak
> xmodmap -e 'keycode 127 = s S aring' > Then, Xvnc will find this mapping for when the viewer sends the aring key; > since the 'aring' key name appears as the _third_ symbol the application > (and you) will see 's' (or 'S') when you press t

Re: xmodmap patch to vnc 3.3.3

2002-03-20 Thread Marius Kotsbak
On Wed, 2002-03-20 at 16:44, Grant McDorman wrote: > According to Marius Kotsbak: > > On Wed, 2002-03-20 at 16:02, Grant McDorman wrote: > > > According to Marius: > > > > Grant McDorman wrote: > > I am NOT using xmodmap with keycodes myself, just keysyms. Th

Re: xmodmap patch to vnc 3.3.3

2002-03-20 Thread Marius Kotsbak
On Wed, 2002-03-20 at 16:02, Grant McDorman wrote: > According to Marius: > > Grant McDorman wrote: > > > > > > How does your dvorak layout modification work? If it's based on keycodes, it > > > will probably not work (keycodes are server dependant). You should be doing > > > something like 'keys