The problem that was previously described here has been solved.
Attachments
Comments 11
I would suggest trying to recreate it on 26.1-snapshot-5 and if it is still an issue for you in that version then provide the type of keyboard as well as video footage of it happening since I would assume they will ask you for both of those things.
I tried this in the latest snapshot, 26.1 Snapshot 5, but the issue persists. It's possible this is because I have an Aceline keyboard. However, I can't provide a video of what's happening because I don't know how to show that I'm pressing the FN key and trying to assign it an action, and no website shows the FN key being pressed. Could you please tell me what method you used when you demonstrated that you were able to assign the jump key to the FN key?
The thing I used is a default setting with my laptop. I don’t believe any software would be able to detect you pressing the FN key if it won’t let you bind it regardless.
From what I’ve read, some keyboards (including certain Aceline models) don’t send a standard key signal for the FN key itself. Instead, FN modifies the signal of other keys, so the operating system never sees “FN” as an individual key press.
That may explain why it can’t be bound on some keyboards but works on others where FN is exposed as a scancode (in my case it showed as scancode.32).
This likely is keyboard specific behavior rather than version specific, but additional reports from different keyboards would help confirm that.
In general, you were right. It turns out that my operating system doesn't really recognize pressing the FN key as a separate keystroke, because this key on my Aceline keyboard is designed to be used in combination with other keys to perform quick actions.
Now I've double-checked all this again, and I couldn't assign the inventory opening to just one FN key, but I was able to do it using the FN+F9 key combination.
The name of the key was displayed as scancode.256. The binding also worked as it should. Thank you again.
I tested this in 26.1-snapshot-4 and was able to bind an action to the FN key successfully. The binding worked as intended, but the key name was displayed as scancode.32 instead of “FN.”