Codex/fix cursor plane lock#460
Conversation
|
Oh, i see you've updated the submodule to avoid building bug i've hit while trying to build the repo following the wiki |
|
Nope, this is incorrect. There is no such commit in the HLab.Avalonia repo, so this still won't build |
|
@mezotaken sorry, thought the enumerable thing was just me. Commit is in this PR: mgth/HLab.Avalonia#1 If you can't wait for merge, you can edit to: |
|
@thomcuddihy
|
|
Not sure about 1 and 2 as it shows clean for me. I'm on Win11 Pro with English locale - mind sharing your build environment?
Regarding 3, I had to do add a helper to load the hook from the correct build location. I'll see about updating that for smarter location finding tomorrow
…________________________________
From: Vladimir Repin ***@***.***>
Sent: Friday, 19 June 2026 20:40:43
To: mgth/LittleBigMouse ***@***.***>
Cc: Thom Cuddihy ***@***.***>; Mention ***@***.***>
Subject: Re: [mgth/LittleBigMouse] Codex/fix cursor plane lock (PR #460)
[https://avatars.githubusercontent.com/u/32306715?s=20&v=4]mezotaken left a comment (mgth/LittleBigMouse#460)<#460 (comment)>
@thomcuddihy<https://github.com/thomcuddihy>
yeah, that's something to do with the language version being set to preview in the project and not fixed. So it changed over time, and the code became obsolete.
it builds after the submodule override, but i have a few issues and i wonder if your build has them as well
1. When it launches, if you open the UI, it opens the window twice
2. There are two debug buttons for exporting/importing config, which weren't there in the distributed version (i've targeted release for my build)
3. I've build the hook and placed it accordingly (LittleBigMouse.Hook.exe near ui .exe file) , but it doesn't launch automatically, the app starts working as expected only after i run the hook manually.
i'm pretty sure that 1 is a code/distributive mismatch and 2,3 are some misconfiguration on my side
—
Reply to this email directly, view it on GitHub<#460?email_source=notifications&email_token=ABIURFOMUARO7DHR6FE6RFL5AUKCXA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZVGA3TQNJUG432M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4750785477>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABIURFPJRUONRFV56B7TLO35AUKCXAVCNFSNUABEKJSXA33TNF2G64TZHMZTANBVGY2TONJ3JFZXG5LFHM2DMNRZG4YDGNZXGOQXMAQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
i did the build in github actions, so the output is an artifact win11 pro too, i don't think there's any issues here i just don't get how it used to work in the first place? like in the version which is attached to releases. there must be some trick to it. Somehow the hook launch is automated in it already. |
|
So the repo version is just slightly different. There are issues, i found out why hook wasn't starting, the |

No description provided.