-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can't get it to do... anything? #4
Comments
Ive also got a system with Open Core Legacy Patcher (and am running into some issues as well in general). Im busy adding some better logging now, and going to test some more on my side. Out of interest, it may be worth try the previous version while I try and diagnose whats going on. |
Thanks for the quick response. I thought I wrote that I did in fact try the
previous version as well. Same thing nothing.
Please let me know if I can do anything to help your testing or if you’d
like to do a remote desktop or anything else
…On Sun, Mar 3, 2024 at 12:33 PM Dylan Vorster ***@***.***> wrote:
Ive also got a system with Open Core Legacy Patcher (and am running into
some issues as well in general). Im busy adding some better logging now,
and going to test some more on my side. Out of interest, it may be worth
try the previous version while I try and diagnose whats going on.
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BESJ5RPZ3WIC2AWAPFPKJS3YWOCJNAVCNFSM6AAAAABEDLKO7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZVGMYTCMZWGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sorry my mistake, my brain went into auto-try-suggest-solutions-mode without even thinking. I have a new version which I think might fix the issue. I discovered that multiple HID devices were being detected for the same device instance but with different usagePage identifiers. The final group-by logic could result in the wrong one being picked. I tested the new version (1.1.0) and my own issues I have been running into seem to be solved, even when I reboot with zero startup-time delay configured. If you try the newer version shortly, I would disable and then re-enable the automatic startup mode which will add the 1.1.0 version to the startup items. Ive also added file logging which can be enabled that should log to the ~/Library/logs/@projectstorm/dynamouse directory (in debug mode). Feel free to share that file if you are are still running into issues with this new version (and are ofc happy sharing it here). If you still run into issues, ill fire up my old 2014 macbook pro running Open Core and then will take a look. Thanks again for helping me make this utility better by sharing your usage of it :) |
(busy with the release now) |
Wow that was fast!
On my Mac, I have a Logitech Bolt USB Receiver and a USB trackball. I thought it would detect both, but it seems to be only one or the other.
When I assigned a mouse to ba screen, it moved the cursor there, but it wasn’t locked to the screen as expected.
Here’s the log. Thanks!

… On Mar 3, 2024, at 2:03 PM, Dylan Vorster ***@***.***> wrote:
Sorry my mistake, my brain went into auto-try-suggest-solutions-mode without even thinking. I have a new version which I think might fix the issue. I discovered that multiple HID devices were being detected for the same device instance but with different usagePage identifiers. The final group-by logic could result in the wrong one being picked. I tested the new version (1.1.0) and my own issues I have been running into seem to be solved, even when I reboot with zero startup-time delay configured. If you try the newer version shortly, I would disable and then re-enable the automatic startup mode which will add the 1.1.0 version to the startup items. Ive also added file logging which can be enabled that should log to the ***@***.***/dynamouse directory (in debug mode). Feel free to share that file if you are are still running into issues with this new version (and are ofc happy sharing it here).
If you still run into issues, ill fire up my old 2014 macbook pro running Open Core and then will take a look.
Thanks again for helping me make this utility better by sharing your usage of it :)
—
Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BESJ5RKDB2LSXIDZ4WTVMQ3YWOM4PAVCNFSM6AAAAABEDLKO7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZVGM3TGNRYHE>.
You are receiving this because you authored the thread.
|
The functionality I am looking for is essentially the same as MouseMux:
https://www.mousemux.com/
I know your app isn’t identical but shares some aspects. The use case is two simultaneous users with their own mouse, keyboard, and cursor for collaboration. There are a lot of tools to do this remotely, but I can’t find anything on a Mac that will allow it locally. With the power of the current generation of Macs, they should easily be able to handle a couple simultaneous web browsing sessions right?
… On Mar 3, 2024, at 2:04 PM, Dylan Vorster ***@***.***> wrote:
(busy with the release now)
—
Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BESJ5RJVCKO7GLNZ54X3W73YWOM6RAVCNFSM6AAAAABEDLKO7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZVGM3TGOBTGA>.
You are receiving this because you authored the thread.
|
Hmm okay so theres a few things here I think:
|
I have a four monitor setup on a Mac Pro 6,1 macOS 14.3.1 (Open Core Legacy Patcher). I installed your 1.0 release, gave it permissions for accessibility, input monitoring, and automation. The app ran fine, identified my devices and screens, and allowed me to assign devices to screens. However when I moved my mice they still moved across all screens. I rebooted, reinstalled, even uninstalled and downgraded to your first release, but nothing worked.
In summary, it seems to install and operate, but it doesn't DO anything.
Logitech USB keyboard mouse
Apple Bluetooth Mouse
PS. Really ant this to work thanks for your efforts!
The text was updated successfully, but these errors were encountered: