b4n left a comment (geany/geany-plugins#1093) > Wouldn't > > https://docs.gtk.org/gdk3/method.Keymap.translate_keyboard_state.html > > help here? I remember I suggested we could use it for Geany in > [geany/geany#1633](https://github.com/geany/geany/pull/1633) and I think this > is the kind of situation where it could help. I'll try.
I didn't re-look deep into the Geany PR (we might want to resuscitate it though), but I don't think it would really solve the issue here, because all that would do is that when I do <kbd>Ctrl+Shift+&</kbd> you get that <kbd>Ctrl+1</kbd> instead of <kbd>Ctrl+Shift+1</kbd>, but it's still won't allow to produce the other one (here, <kbd>Ctrl+Shift+1</kbd> will not be possible to generate</kbd>). So yeah, it somewhat "fixes it" in the logical key interpretation, but it doesn't solve the issue for a French layout. Worse, I would imagine it might break it somewhat with any layout, as it's likely the generated keyval is different with <kbd>Shift</kbd>, and thus you'll always get <kbd>Shift</kbd> stripped, and then even the `iShiftNumbers` hack wouldn't work on US layouts. I might be missing something, but AIUI using keysyms is fundamentally flawed when what is actually meant is *"whatever combination generates N, but with <kbd>Shift</kbd> added or removed"*. basically, what is actually expected is a physical key, not the keysym it generates. > Apart from that, I tested what happens on Windows with the current g-p state > and Ctrl+Shoft+num launches some system applications so it may even be > possible that this keybinding will be unavailable there. That's an argument in favor to regular, customizable shortcuts. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1093#issuecomment-3008381376 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany-plugins/pull/1093/[email protected]>
