Once you check "Hide after releasing all pressed modifier keys," the floating menu stays hidden even if you uncheck the option; creating a new, different menu won't restore the old behavior.
Pasting text from the "choose from list" action fails.
The context menu steals focus.
Creating or modifying JXA often causes it to stop responding; you have to force-quit before you can continue configuring.
In the secure input field, you have to press the shortcut key several times before the action is triggered.
After a key-sequence group is disabled, its trigger still fires, but no action is performed.
When remapping multiple keys, there's a significant delay in subsequent actions.
Sometimes a trigger will stop working for no clear reason—no matter how you tweak it, something’s still off—yet the moment you recreate it from scratch, the problem vanishes.
The trigger column suddenly became wider, and the minimum width setting had no effect.
"text selection did change"—in Chrome, selecting text triggers cmd+c; Chrome should be able to grab the text directly, right?
3, 5, 6, and 10 are mostly expected. For secure input fields macOS always enables the secure input mode, which requires BTT to fallback to a compatibility shortcut mode that disables lots of the shortcut functionality and may take a moment to engage. If your shortcut needs to work while secure input is active make sure you don't use FN in it and it doesn't only have shift and/or option as modifiers.
Unfortunately 8 is too unspecific, there is not much I can say about that without more information as tons of things can influence this.
For 7, what exactly do you mean by remapping?
I can reproduce 2. I'l add a workaround to the next alpha giving back key focus to the previous window before triggering the action.
For 4. do you have an example JXA that has caused issues? I'm using a lot of scripts here but haven't encountered anything weird yet.
For 1. could you quickly describe your usecase?
If possible, please always create separate posts for bugs. As I'm only using this forum to prioritize it is very hard to prioritize & track if multiple are put into one post.
So, this post mainly reports the issue with the floating menu; other noteworthy problems will be covered in a separate post.
For 1, I have a floating menu—similar to PopClip—that I trigger with a hotkey, and it used to work fine. Lately, though, I checked “Hide after releasing all pressed modifier keys” in Show floating menu action. Even after unchecking it, the behavior hasn’t changed; even a brand-new menu follows the same rule, as if the option were hard-coded. The menu always hides the moment I release the shortcut.
By the way, regarding issues 7 and 8, I can’t reproduce them—they only crop up occasionally. I’ll follow up with more specifics if they happen again.
For 7, repeatedly setting Remap Keyboard Key (Low Level) caused subsequent actions to respond very slowly under certain conditions. I've already switched to a different approach to achieve my goal. I just tested it and can no longer reproduce the issue. If I run into specific problems later, I'll provide feedback.
For 8, some triggers inexplicably fail to fire, but duplicating or recreating them fixes the issue. I can’t reproduce it either—it’s something I’ve run into over long-term use of BetterTouchTool, and I never know why.
Update: Triggering the floating menu via a shortcut causes the issue above, and the “Close On Any Keyboard Input” option has no effect. However, triggering it via gesture or clicking the eye icon in the UI won’t cause any issues.
