Blockland Files > Add-Ons
[Support] EventScript - Sharing events for the future
Dannu:
For Mac keybinds, look at the new duplicator. Zeb did some trial and error with me testing and we figured out how to make natural cmd-keybinds.
mctwist:
Well, I checked it just now and found out that you guys are just overriding the current system with your own map. I doubt that'll help me as the user needs to be able to change it himself.
Of course, I could go way around people and add my own keybind completely overriding any other keybinds existing. I'll ponder on that and will see what I can conclude from it.
Edit: I looked into it. Doable, but I'll see if it'll look alright. I'll do as he does by forcing the keybinds no matter what.
Edit2: I've made a fix for it. I'll check with a Mac user on Discord if it's fixed.
mctwist:
I tried the fix with a Mac user but apparently it didn't work. It's almost exactly of how Zeblote does it, but the only difference is what keybinds. We think it is that the cursor is locked to an input field, and therefore disabling keybinds for Mac.
Shift Kitty:
The keybinds are only forced if the user hasn't set their own.
Dannu:
--- Quote from: mctwist on February 07, 2018, 06:04:32 AM ---We think it is that the cursor is locked to an input field, and therefore disabling keybinds for Mac.
--- End quote ---
If this is the issue, it might be caused with what type of bindings you use. Just browsing through the .dso source, I notice that most of the common keybinds (e.g. moveforward, brick controls) use moveMap.bind(...). However, some more important keybinds such as toggleConsole, toggleFullScreen, etc use GlobalActionMap.bind(...)
For example:
--- Code: ---GlobalActionMap.bind(keyboard, "tilde", toggleConsole);
GlobalActionMap.bindCmd(keyboard, "alt enter", "", "togFullScreen();");
GlobalActionMap.bindCmd(keyboard, "F1", "", "contextHelp();");
--- End code ---
moveMap is just declared in the .dso with:
--- Code: ---new ActionMap(moveMap){};
--- End code ---
However, GlobalActionMap isn't created anywhere in the .dso source, meaning that it is more than likely created in the engine, possibly giving it special properties.
Somewhat speculative, but worth investigating in my opinion.