Replies: 2 comments
-
|
Create an AutoHotKey script that kills and restarts the process(s) |
Beta Was this translation helpful? Give feedback.
-
|
I'm having a similar issue, so I'll go a little further on my comment. LBM conflicts with anything that locks the cursor to a monitor area; in my case, it's with Dual Monitor Tools (DMT). I've tried to solve this with an AHK2 script that I mangled together, but with no luck; the script is not fast enough, fixes the error, but loses LBM functionality. I'll leave the script below if anyone wants to use it, but the true ideal solution, IMO, would be a toggle key inside LBM, "only activate when 'key' is pressed down" . |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Allow the user to toggle start/stop with a hotkey of their choosing.
When playing a game that locks the mouse cursor to a window (whether fullscreen, borderless, or otherwise), the cursor refuses to stay locked on the game window. Eventually, it'll register a click on a single pixel of a neighboring monitor during gameplay, causing the game to lose focus. This is just a general issue with playing games while using more than one monitor on Windows.
I discovered that you can prevent mouse crossover between monitors in Windows settings (see photo below) and just use LBM exclusively for monitor placement. This way, I can stop LBM when I am gaming (while ensuring the mouse stays on the desired monitor), and start it again when I want to crossover with my mouse. A hotkey for the 'start' and 'stop' actions (or a toggle for them) would simply allow me to forgo the extra action of doing such from my task tray.
I hope my meaning here is understood. Thank you for this wonderful program.
Beta Was this translation helpful? Give feedback.
All reactions