Open Madd0g opened 3 years ago
Is it just Hammerspoon created menus that don't work with the accessibility tools you're using? Or all "extra" menus?
And what accessibility tools are you referring to? Hammerspoon built ones or third party?
I have a possible menubar replacement module for Hammerspoon that I'm hoping to get to work on again in December or so that addresses some of my issues with the existing module (e.g. being able to change the menu items while it is open, create submenus as needed as opposed to pre-populating them when populating the main list, recognizing variant items when modifiers held down (like the Finder's file menu when you press Option), etc.)
One of the things I remember being an issue was that hs.timer
was queued such that it was blocked while a menu was open, but hs.eventtap
wasn't... I think I know the fix, but that's the kind of thing I want to revisit before submitting the module for review... If the issue is only with Hammerspoon menus, and if you can give me more details of specifically what isn't working for you, I may be able to add it to my tests and see if we can find a work around for it in the replacement module.
One of the things I remember being an issue was that
hs.timer
was queued such that it was blocked while a menu was open, buths.eventtap
wasn't
the things that didn't work for me:
trishume
, doesn't register ANY command while menu is openhs.eventtap.event.newKeyEvent
doesn't workIs it just Hammerspoon created menus [...] Or all "extra" menus?
not sure what you mean by extra, if you mean menus created by other apps (not os default), then they don't have this keyboard nav issue.
I know about chooser (I would use that if it wasn't search-oriented).
I put a bunch of things in a regular
hs.menubar
and it mostly worked great for me, but menus appear to be very special in the way they're blocking input (accessibility tools couldn't send keys to it), so I'm looking for alternatives to:Thanks