ForwardFeed
ForwardFeed
Ah, the bridge confuse me,i don't know how to patch properly then. my patch is really simple it just holds in: ```py from keyboard import add_hotkey add_hotkey(Hotkeys.pause_hotkey.default, self.pause_hotkey_pressed) add_hotkey(Hotkeys.break_hotkey.default, self.break_hotkey_pressed)...
My apologies, for some reason i didn't know we could change hotkey. I think i can deal with that.
Now global hotkeys are dynamically set. And it was working fine but it's possible some keys i haven't tried be cause of trouble.
I just re cloned my fork and retried and it works, that's so awkward why does it not work? it is the library that isn't working? try alone this snippet...
In case this is not working try this ``` from keyboard import read_key while 1: print(read_key()) ``` Then you press any key and it will return the key corresponding to...
Okay i have found a bug while trying to understand how it couldn't have worked. If i set a hotkey to nothing and click to validate it break the thing...
It's fixed
Maybe using the import/export field is better, Just adding a export calculation button and using the import field to just paste a Base64 or JSON Text
Well, i'm doing it, and nevermind i agree the path variable is the most practical for end user
I don't know either, i believe the issue isn't on the rust call end but more on the C end. But i really don't know much how it works. The...