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
Copy file name to clipboardExpand all lines: README.md
+5-12Lines changed: 5 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ When you first start DynaMouse and start configuring it, you will be asked to en
19
19
## Features
20
20
21
21
* Works as a system tray, doesn't appear in the dock
22
-
* Supports infinit monitors and pointer devices
22
+
* Supports infinite monitors and pointer devices
23
23
* Assign multiple mice to the same monitor
24
24
* Configure specific mice to be uncontrolled (not governed by DynaMouse)
25
25
* Each mouse's position is remembered on each screen
@@ -37,18 +37,11 @@ The devices below have been tested and work:
37
37
* Apple magic trackpad (MMMP3AM/A)
38
38
* M1 Macbook trackpad
39
39
40
-
## Updating
40
+
## Troubleshooting
41
41
42
-
If you are updating to a newer version, you will need to first completely remove the assigned permissions in System Preferences
43
-
by pressing the minus button for both 'Input Monitoring' and 'Accessibility'. The reason for this is because the MacOS sandboxing system
44
-
sees the new version as having different code signature (hash) and throws the error:
45
-
46
-
`Failed to match existing code requirement for subject projectstorm.dynamouse and service kTCCServiceListenEvent`
47
-
48
-
I would appreciate some help on fixing this :)
49
-
50
-

51
-

42
+
* You can enable file logging which will log to `~/Library/Logs/@projectstorm/Dynamouse` (this can help with submitting an issue)
43
+
* Apple startup items seem use the exact binary at the time of installation, so if you are updating to a newer version, try disabling and re-enabling startup mode to install the newer version of the software
44
+
* You may need to remove and re-add Dynamouse accessibility permissions across versions (but I seem to no longer run into this after version 1.0.0)
0 commit comments