4 ms·

I tried this, I started gedit then xwininfo to get the window id then xev -id and then started typing in gedit. I saw event information but didn't see what char

by jebblue 13y ago

I tried this, I started gedit then xwininfo to get the window id then xev -id and then started typing in gedit. I saw event information but didn't see what characters were being typed so what's the point you're trying to make?

FreeFull 13y ago
I do see what characters are getting typed when I do the same thing. For example: KeyPress event, serial 28, synthetic NO, window 0x2000003, root 0x2b7, subw 0x0, time 322414662, (225,283), root:(1057,269), state 0x0, keycode 26 (keysym 0x65, e), same_screen YES, XLookupString gives 1 bytes: (65) "e" XmbLookupString gives 1 bytes: (65) "e" XFilterEvent returns: False
- jebblue 13y ago
  I barely see half that information so something's different about how we're doing it. I'm Ubuntu 12.04 btw.
  - FreeFull 13y ago
    Do you see all the information when you let xev make its own window rather than look at a different window?