Issue when revoking BD Accessibility permission

[oldpcguy]

20-30 min after install and exploring BetterDusplay I got onscreen message saying "Let's fix this now" and verbiage about giving access to BD for keyboard control of sound/brightness. I assume for the dummy displays.

I gave permission to BD in Privacy Settings> Accessibility. After a short while I questioned if I should have done so. So, I revoked (unchecked) access for BD and immediate result was lost all keyboard and some mouse control.

Pressing keys had no effect; I could move my mouse pointer but not click and get response. Had to force shutdown using power button. Pressing button gave option to restart but no keyboard or mouse ability to respond.

Running Mac Studio M1 Max on Monterrey 12.5, Magic Keyboard for Apple Silicon, Magic Mouse, dual monitors: Dell UP2516d and Dell U2415. Decided to uninstall BD and do OS recovery. Now reporting issue but still interested in even buying Pro version. Will wait for feedback before reinstalling BD.

Had not read full feature set of BD prior to install but after doing so I don't think I need dummies, unless USB-C to mDP (1.2) with cable adapter is not native. I'm now using aftermarket adapter but didn't try without BD dummy.

Possibly genuine Apple adapter would be native? Mac Studio has native HDMI but not mDP. Will be replacing Dell U2415 with UP2716d (Could not find any new 27" UHD with 10-bit in any brand). Please advise about native support.

[waydabber]

Hi, keyboard control is not needed for dummy displays, it is needed to use the native brightness/volume keys of the Apple keyboard to control display brightness and volume. Enabling or revoking accessibility permissions does not have any effect on how other stuff works and certainly cannot disable general interaction with the OS.

The most likely explanation is that you probably had enabled a dummy connected was off-screen and probably some kind of top-level modal dialog popped up on that screen waiting for you to click on it but you could not (since you did not see it) - this is why interaction was limited - it probably had nothing to do to changing accessibility settings. But it is just my best guess (it does not make much sense to connect a dummy unless you mirror it to your main screen or show it via a PIP window or use that screen with some streaming app or other purposes for example).