Removing accessibility permission breaks the cmd key

[gitgetgot]

I'm using a MacBookPro 2015, Mojave, AltTab v3.15.0.

At first start of AltTab, I need to create and activate this:

When I -for whatever reason- DISABLE it

the CMD key is inacessible anymore,
I cannot use systemwide CMD+TAB to navigate anymore,
but I can use ALT+TAB (as configured by default in AltTab) to navigate.

Exiting AltTab ends this strange behaviour, where it seems, that CMD key is not working anymore (not possible to start spotlight via CMD+SPACE or take a screenshot with CMD+SHIFT+4)

Same odd behaviour, when I configure CMD instead of the ALT key in AltTab

Same odd behaviour was in older version of AltTab too.

Re-Activating, as in the first screenshot, and everything seems normal again.

[lwouis]

You are disabling the permissions while already using AltTab, correct? This is currently not supported unfortunately. There is a ticket to support that (kind of): #127.

Currently, the app only check permission at launch-time, not during runtime.

I don't think many people change the permissions while running the app. Also the issue goes away if you restart the app as it asks you again for permissions, or if you re-enable the permission.

You said "When I -for whatever reason- DISABLE it". Could you help me understand what's your use-case to disable the permission while the app is running?

Discussing support a bit more: we could observe the permissions easily I think. The problem is that we could just quit the app if they are removed. That's pretty cheap to do but bad UX. The real UX needs to include other aspects of nicely communicating what's happening to the user. This again should be fleshed out in #127

Update: I had read your description wrong. You're saying AltTab still works after removing permission, but the cmd key stops working? That's very odd that AltTab keeps working.

Give me some time, I'll try to see what happens on my machine when I do this.

[lwouis]

@gitgetgot I released a new version of AltTab which quits if you the permission is removed during runtime. It's a first quick win, as the app doesn't swallow keyboard inputs now. A more advanced UX can now be discussed in #127.

Also I'm still curious about your use-case of disabling permissions during runtime. Why do you need to do such a thing?