Newbie Problem - impossible to enter numbers in the sub-tracks (Chance, velocity,...)

[kjetil]

Seems like we're getting the wrong value from libxcb/xkb, somehow, that's surprising. I have to create another release candidate I hope you have the time to test. But do you have a special keyboard? (How many keys are there to the left of the "1" key?) Do you have another keyboard you can try?

[kjetil]

I've made a new version, same url as last time:
https://radium.dog/radium_64bit_linux-7.5.77.tar.xz

Same procedure as last time, but the program is much more noisy now, so if you could make sure to only copy the lines printed to the terminal when pressing "1", that would be great.

My output looks like this:

Code: Select all

DEBUG/get_sym: Enter. event->detail: 10
DEBUG/get_sym: Enter. event->detail: 10
DEBUG/keysym_to_keynum: Enter. keysym: 49. XK_1: 49. XK_3: 51
DEBUG/VELTEXT_keypress: Enter. realline: 4. Place: 4 + 0/1. key: 39
DEBUG/VELTEXT_keypress: subsubtrack: 0
DEBUG/VELTEXT_keypress: Branch 2
DEBUG/DAT_get_newvalue: subsubtrack: 0. Key: 39. default_value: 52428. default_logtype: 0. min_value: 0. max_value: 255. is_hex: 1
DEBUG/DAT_get_newvalue: base: 16. num_subtracks: 2. val: 1. EVENT_1: 39
DEBUG/get_sym: Enter. event->detail: 10
DEBUG/get_sym: Enter. event->detail: 10
DEBUG/keysym_to_keynum: Enter. keysym: 49. XK_1: 49. XK_3: 51

I guess your output might have a different value for event->detail, but I don't know what's happening.

[elode]

I have two keyboards:
- an X-bows Nature, which is indeed a bit peculiar
- a DELL with numeric keypad, a rather standard keyboard.

Of course I tried with my two keyboards to see if it wouldn’t be because of my X-bows Nature, but the result is the same. I even tried various keyboard drivers without more result.

My two keyboards have only one key to the left of the "1" key.

[elode]

The result with your new version of Radium:

Code: Select all

DEBUG/get_sym: Enter. event->detail: 10
DEBUG/get_sym: Enter. event->detail: 10
DEBUG/keysym_to_keynum: Enter. keysym: 34. XK_1: 49. XK_3: 51
DEBUG/VELTEXT_keypress: Enter. realline: 1. Place: 1 + 0/1. key: 41
DEBUG/VELTEXT_keypress: subsubtrack: 0
DEBUG/VELTEXT_keypress: Branch 2
DEBUG/DAT_get_newvalue: subsubtrack: 0. Key: 41. default_value: 52428. default_logtype: 0. min_value: 0. max_value: 255. is_hex: 1
DEBUG/DAT_get_newvalue: base: 16. num_subtracks: 2. val: 3. EVENT_1: 39
DEBUG/get_sym: Enter. event->detail: 10
DEBUG/get_sym: Enter. event->detail: 10
DEBUG/keysym_to_keynum: Enter. keysym: 34. XK_1: 49. XK_3: 51

[kjetil]

You have a different value for keysym than me. Instead of "XK_1" you have "XK_quotedbl" (i.e. single-quote).

I get XK_quotedbl as well when I press the single-quote key, but not when I press the 1 key.

Does shift/capslock/numlock/etc. change the situation?

In this line:

DEBUG/keysym_to_keynum: Enter. keysym: 34. XK_1: 49. XK_3: 51

You are supposed to see "keysym: 49", not "keysym 34"

[elode]

No, the fact of activating Caplock doesn’t change anything. I still have:

Code: Select all

DEBUG/keysym_to_keynum: Enter. keysym: 34. XK_1: 49. XK_3: 51

[kjetil]

Seems like I've used functions that haven't been used very much used earlier (not many hits when searching the internet). The simple workaround is to use Qt to get numbers from the keyboard instead of querying X11. But have you noticed any other problems with the keyboard?

[elode]

No, it’s the first time this kind of thing has happened to me.

[kjetil]

I meant in Radium. If you have seen any other wrong keyboard behavior than getting numbers?

[kjetil]

Does the key "2" add a "C#", the key 3 add "D#", the key 5 add "F#", the key 6 add "G#", the key 7 add "A#", the key 9 add "C#", and the key 0 add "D#"?

If they do, we can use scancode instead of using Qt to get the numbers, which is simpler, although a bit hacky.