-
-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐞 Keybinding import/export bug. 1.2.0 (1401) #652
Comments
It looks like the problem is that is is NOT saving and loading the correct trigger key. |
The trigger key currently doesn't save in the exported keybinds file. But that would make sense, will try and implement this tomorrow! |
I got the update, and tried it, but now it crashes after the import. |
Would you be able to send your keybinds file here? I will try importing it on my end. (from the latest version, unlike the one in your original report?) Edit: or is this happening when importing the original file? |
I just verified, and it's the same as the first zip I sent. No changes. |
Try the latest development build, should be fixed now! |
so far, so good... thanks, I'll report anything new if it comes up. |
Bug Description
2 dev builds have come out today, and as I was about to report the issue on the first one, another update came along, so I tried it too, and same problem.
I export my keybindings on one Mac, and try to import on the 2nd Mac, and they are all wrong.
It changed the 3 key combo (ctrl, cmd, alt) to fn.
I don't have a Mac fn key on my keybopards.
So, I am using the 3 modifier keys and the keypad.
To move the windows top, bottom, left, right, corners, and center.
When I import the file on the 2nd Mac, they are all wrong.
Source Mac is on Sonoma 14.7.1
Destination Mac is on Sequoia 15.2
Both are on Loop 1.2.0 (1401)
Steps To Reproduce
4
Expected Behavior
For the keybindings to be correct.
Actual Behavior
Changes the 3 modifier keys to a non-existent mac-fn key.
Screenshots
Loop Keybinds.json.zip
macOS Version
15.2 (24C101)
Loop Version
1.2.0 (1401)
Additional Context
No response
Final Checks
The text was updated successfully, but these errors were encountered: