You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Metropolitan sandwich
OP
— Today at 2:18 PM
Because stubborn people (me) want to change the restart keybind from f10 to something else (me) and that this pressing issue affects my experience on this platform (it doesn't but I opened twitter earlier and needed to put a bullshit opinion somewhere)
Response
kate! — Today at 2:32 PM
Heya!
I will look into adding that as a feature in the next minor update/patch since it's been bugging me a bit on my deck. But this might take a bit longer than I'd want since we're currently going through a heatwave where I live.
The F10 keybind gets detected from a different process that doesn't have access to everything that the actual app does (just incase if something crashes).
The text was updated successfully, but these errors were encountered:
Made initial prototype, not using the existing keybind system since I would have to port chord parsing to the main process which I don't want to do at the moment.
Here is a video demoing the current prototype which will be good enough to create a PR and close this issue.
It might be viable in the future to move all of the keybind system to the main process then trigger events by calling the renderer from the main process which will then emit an event on a local event emitter which things would listen to inorder to implement the keybinds.
This issue was created in reference to the "Keybind options" thread in the "feature-request" forum.
Original request
Response
The text was updated successfully, but these errors were encountered: