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
it seems LiveSplitOne doesn't detect inputs sent by a 3rd party program, I tried to use Toufool's AutoSpliter on Linux (Ubuntu 24.10 with KDE X11) with this and when it's supposed to split LiveSplit doesn't split. Note that the autosplit program sends inputs properly (though I don't know how they're doing that), as a test I set my split key to the letter/key "A" and it typed it in a textbox, hence why I'm reporting this here as it seems to be related to this project specifically, also not sure if it works (or not) on the other operating systems
Edit: I forgot to mention it but I'm using the desktop version, that said I also tried on the website and same behavior (with the page focused/active)
I did more tests today (this time after cloning and building the repo), it seems it only happens in the "run" view (so like, the window you have when you are doing a run) specifically on linux on the desktop version, it worked on the web version apparently (I think the last time I assumed it was using the system's keyboard layout but it assumes qwerty for everything)
I tried to figured out where exactly but idk I'm getting lost, though it seems the only difference is the livesplit-hotkey crate? I noticed a comment about it being stubbed when compiled but idk I don't understand everything, I hope the core issue isn't located in tauri
so basically the autosplitter I mentioned (and onboard) works on the web version, also another oddity I just noticed: on the web version my A button (french keyboard layout) is mapped to Q when I set the hotkey, but on the desktop version it's mapped to A, which is weird
Activity
[-]Hotkeys not recognized in some scenerios[/-][+]Hotkeys not recognized in some scenarios[/+]Avasam commentedon Mar 16, 2025
I'm not the most knowledgeable on Linux side, but here's a bit of additional context that may help with troubleshooting. AutoSplit uses
keyboardto send "simple" hotkeys: https://github.com/Toufool/AutoSplit/blob/3cac447485087529f1d0ade2b308810e439fd5c9/src/hotkeys.py#L130Which uses a Fake uinput Device to send events:
https://github.com/boppreh/keyboard/blob/d232de09bda50ecb5211ebcc59b85bc6da6aaa24/keyboard/_nixkeyboard.py#L155-L157
https://github.com/boppreh/keyboard/blob/d232de09bda50ecb5211ebcc59b85bc6da6aaa24/keyboard/_nixcommon.py#L139-L169
For more "complex" hotkeys (such as
shift+A), pyautogui is used https://github.com/Toufool/AutoSplit/blob/3cac447485087529f1d0ade2b308810e439fd5c9/src/hotkeys.py#L138-L141which uses Xlib keypress events:
https://github.com/asweigart/pyautogui/blob/b4255d0be42c377154c7d92337d7f8515fc63234/pyautogui/_pyautogui_x11.py#L143-L151
https://github.com/python-xlib/python-xlib/blob/4e8bbf8fc4941e5da301a8b3db8d27e98de68666/Xlib/ext/xtest.py#L93-L103
Yanis002 commentedon Mar 27, 2025
I did some tests out of curiosity:
onboard), it doesn't work apparentlyso basically it seems to be a Linux-only issue (and probably affecting any virtual keyboards)
Reference LiveSplit/LiveSplitOne#1025
Yanis002 commentedon Apr 4, 2025
I did more tests today (this time after cloning and building the repo), it seems it only happens in the "run" view (so like, the window you have when you are doing a run) specifically on linux on the desktop version, it worked on the web version apparently (I think the last time I assumed it was using the system's keyboard layout but it assumes qwerty for everything)
I tried to figured out where exactly but idk I'm getting lost, though it seems the only difference is the livesplit-hotkey crate? I noticed a comment about it being stubbed when compiled but idk I don't understand everything, I hope the core issue isn't located in tauri
so basically the autosplitter I mentioned (and onboard) works on the web version, also another oddity I just noticed: on the web version my A button (french keyboard layout) is mapped to Q when I set the hotkey, but on the desktop version it's mapped to A, which is weird