> Greg Ercolano wrote: > > fhools wrote: > >> I am running fltk 1.3.x on aix 5.3 with Exceed as the X server. > >> > >> Ctrl-C and Ctrl-V in Fl_Input input field does not work, instead a 'c' or > >> 'v' is inserted. I also tried the test/keyboard application > >> and event_text shows as 'c' or 'v' > >> > >> I tried fltk 1.1.10 and it works. test/keyboard application shows ^C or ^V. > > > > In the test/keyboard app: is the CTRL key stripped off /all/ keyboard > > sequences > > (^A, ^B, etc) in fltk 1.3.x, or is it just ^C/^V? > > > > How about the other modifier keys; SHIFT and ALT and META; are they all > > stripped as well? > > > > Does the state of CapsLock, NumLock or ScrollLock affect this? > > > > I'm not too knowledgeable about the X keyboard stuff that changed > > between > > 1.1.x and 1.3.x, but more info might help the devs. > > Since I don't know much about this, but am the first to respond, > my first guess is sniff around in src/Fl_x.cxx -- that's where much > of the X specific code is. If motivated and X knowledgeable, you may > be able to find the problem before the devs. > > xdiff(1)ing 1.1.10 against 1.3.x for that file, I see a lot of new > X Input Method (XIM) stuff was added in 1.3 to support multiple > languages.. > might be something to do with that. > > The man page on XOpenIM indicates locale is taken into consideration, > so possibly LOCALE settings are coming into play here as well, eg: > > locale > printenv | egrep 'LC_|LANG'
So I did some more tests. The other modifier keys don't really change the event_text, neither in 1.1 or 1.3. The Capslock/Numlock/Scroll lock doesn't change anything either. I got access to a solaris system and ran fltk 1.3 and the keyboard app showed the correct ^C/^V response. I believe its a problem with X Input Methods on the AIX 5.3 machine I'm running on. The Solaris system did not have a problem with XCreateIC (XIM). _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
