I was trying to make (number pad of full layout keyboard) keypad 0 as globe key and does but its limited! I can't use this for native window management hotkey for some reason but the normal command like globe + C or E works
did you try it via the low level key remap functionality? I think the systme offers multiple different FN/Globe keys that behave slightly different, I‘m currently not on my Mac, but you could try the multiple variations - one of them should work.
Weird, it seems to work fine here with the window management shortcuts - even regardless of whether I assign "standard globe / fn / function as modifier" or "globe / fn / function as key"
Unfortunately BTT does not have any further control over this, it basically just tells the system what shall be remapped but how that is handled is entirely up to the system and running outside of BTT's process.
I remember it used to work in earlier builds
you mean previous macOS builds or BTT? (for btt the remapping has never changed, mostly because there is only one API that allows to do this low level remapping)
both as I have updated to latest Mac os 26.6
I have just installed karabiner and it is handling globe key well enogh and the window navigation shortcut works via that @Andreas_Hegenberg why karabiner is better in doing that?
karabiner works at a much lower level (which comes with its own lot of issues), which allows it to handle things differently. BTT can only make use of the system provided remapping functionalities.
(However I just checked with another keyboard of mine and remapping to fn also works fine there - might be something else that is interfering here)
I also tried with my another keyboard, that was also not working for me!
I tried visualising the remapped keys via key sequence and find something interesting, the arrow key trigger different keycode somehow
can you check this out!? @Andreas_Hegenberg
The native window navigation shortcut having arrow left, right, up, down, when combined with globe key they change to home, end, page up, page down (and this is the reason why the shortcut not behaving as it should)
Can you adjust so that when Fn or globe combined with arrow key then automatically could change to home, end, page up, page down
if a real FN key press is active, macOS changes the arrow left/right key to a page up/page down key, that is indicated by that different symbol. In your remapped case the modifier does not seem to be detected by the system (which is also why it says "Key Down" instead of "Modifier Down" for FN.
Do you currently have it remapped to "standard globe / fn / function as modifier" or "globe / fn / function as key" ?
that explains the issues you are seeing, but unfortunately I don't know how to resolve it. This might be a macOS limitation with some keyboards.
You could try whether the macOS integrated remapping works (quit BTT, possibly disconnected and reconnect the keyboard to make sure the state is clear) using this terminal command:
(remaps keypad 0 to fn as modifier)
hidutil property --set '{"UserKeyMapping":[{"HIDKeyboardModifierMappingSrc":0x700000062,"HIDKeyboardModifierMappingDst":0xff00000003}]}'
This terminal command too not working! Look like MacOS sending fn+ arrow configuration of home/end/pageup/page down from hardware level- as software not adding these up! So, the karabiner somehow was adding them on software level via
fn + left= home
fn + right = end
fn + up = page up
fn + down= page down
it seems like for some reason your system is always remapping to the "fn as key" and not "fn as modifier" using the apple API's. This might be intentional to not allow third party keyboards to behave the same as apple keyboards.
In that case Karabiner might be the only solution that can workaround this.