I have tested this as far as I can. I prompted ClaudeAI for help with this, and had it prepare the following summary.
Bug Report: Floating Menu Triggers Intermittently Render with "No Entry" Warning Overlay in Configuration Window
Reported by: Kirby Krieger
Component: BetterTouchTool Configuration window — Custom Floating Menus trigger list
Build: Latest Alpha as of 2026-07-07 (6.622)
macOS version: (26.5.1 (25F80))
Executive Summary
After duplicating a Custom Floating Menu, their rows in the Configuration window's Floating Menus list began rendering with an inverted/reverse-video color scheme and a pink "No Entry" (circle-with-slash) icon superimposed on the Floating Menu's icon. The triggers on the affected Floating Menus continue to function correctly when activated — this appears to be a purely cosmetic rendering issue confined to the Configuration window's Floating Menu list, not a functional fault.
Key findings from testing so far:
- The warning state is not tied to a missing or broken icon image. The Icon Inspector for an affected trigger shows default, unmodified settings (Icon type: "From Image File," no image assigned) — identical to the default state of unaffected triggers.
- The warning state spread to a previously unaffected Floating Menu simply by opening its Icon Inspector section to inspect (not change) its settings. No values were altered.
- The warning state has since propagated to at least one sub-Floating-Menu inside an affected Floating Menu, despite that sub-Menu never having been directly selected, opened, or edited.
- Across six Floating Menus visible in the list, three show the warning state and three do not, with no correlation to the number of items/triggers each menu contains (see screen-grab).
- Toggling the Icon source between "From Image File" and "From SF Symbols" has no effect on the warning state.
- Clicking the small circular refresh/reset icon next to the icon swatch triggers a visible redraw (a quick flash) but does not clear the warning state.
- Upgrading to the newest Alpha build (which restarts BTT) and manually restarting BTT again did not resolve the issue.
- Rebooting the computer did not resolve the issue.
This report is a live, ongoing investigation rather than a fully diagnosed root cause — the trigger condition for why a given trigger flips into the warning state has not been identified. Item count, icon source, and app restarts and computer reboot have all been ruled out as causes.
