[FreeNX-kNX] problems with Mac OS X client
perkel
perkel at u.washington.edu
Fri Aug 19 20:09:18 UTC 2005
Again, thanks and you've gotten be a bit further, but I'm stuck again.
I used xev on my Mac to determine the keystroke and keysym generated by
shift-8 and by the numeric keypad '*'. In both cases they seem appropriate:
[from shift-8]
KeyPress event, serial 24, synthetic NO, window 0x800001,
root 0x57, subw 0x0, time 31647633, (13,-9), root:(33,55),
state 0x0, keycode 64 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes: ""
KeyPress event, serial 24, synthetic NO, window 0x800001,
root 0x57, subw 0x0, time 31647849, (13,-9), root:(33,55),
state 0x1, keycode 36 (keysym 0x2a, asterisk), same_screen YES,
XLookupString gives 1 bytes: "*"
KeyRelease event, serial 24, synthetic NO, window 0x800001,
root 0x57, subw 0x0, time 31647906, (13,-9), root:(33,55),
state 0x1, keycode 36 (keysym 0x2a, asterisk), same_screen YES,
XLookupString gives 1 bytes: "*"
KeyRelease event, serial 24, synthetic NO, window 0x800001,
root 0x57, subw 0x0, time 31648014, (13,-9), root:(33,55),
state 0x1, keycode 64 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes: ""
[and from fn-P]
KeyPress event, serial 24, synthetic NO, window 0x800001,
root 0x57, subw 0x0, time 32240898, (14,-9), root:(34,55),
state 0x0, keycode 75 (keysym 0x2a, asterisk), same_screen YES,
XLookupString gives 1 bytes: "*"
KeyRelease event, serial 24, synthetic NO, window 0x800001,
root 0x57, subw 0x0, time 32240955, (14,-9), root:(34,55),
state 0x0, keycode 75 (keysym 0x2a, asterisk), same_screen YES,
XLookupString gives 1 bytes: "*"
So both are correctly generating keysym 0x2a. This is also what I see
in xmodmap -pk. So is it reasonable to conclude that somewhere
downstream the keysym is getting changed? In any case, do you have any
suggestions for how to proceed in figuring this out?
Thanks again,
David
Jesse Byler wrote:
> On Friday 12 August 2005 15:52, perkel wrote:
>
>>Thanks for this suggestion. Unfortunately, I'm still missing
>>something.
>>
>>I can start the X server, open xterm and do the xmodmap step and
>>can confirm that this has had the desired effect by checking with
>>xmodmap -pk.
>>
>>But then when I use nxclient (or even ssh -X to another machine)
>>and then open konsole, I still don't get '*' or '+' from the normal
>>keyboard locations (shift-8 or shift-=). I do also confirm that
>>these characters from the numeric keypad work fine. So at this
>>point I don't even know what to try next.
>
>
> What you can do is use the xev program to see what keycodes the
> regular * and + keys are sending, and then assign these keycodes to
> the * and + keysyms using xmodmap. The keycodes in my .Xmodmap are
> for my Pismo; if they don't work for you you can use xev to find the
> ones that will work for your keyboard.
>
> Also, although it appears that both xmodmap and xev use decimal
> keycodes by default, if you still have problems make sure one of them
> isn't using hex.
>
>
>>Also, although I'm clearly not ready for this yet, I was unable to
>>find source for session_gate. Any pointers?
>
>
> Hmm, try this:
>
> http://web.mit.edu/afs/dev/source/src-current/athena/bin/session/
>
> Hope that helps!
> -Jesse
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
--
David J. Perkel, Ph.D., Associate Professor |
Departments of Biology and Otolaryngology |
University of Washington |
1959 NE Pacific St. HSB BB 1165 | Tel. 206-221-2477
Box 356515 | FAX: 206-543-5152
Seattle, WA 98195-6515 | perkel at u.washington.edu
More information about the FreeNX-kNX
mailing list