Glimble 0.1.5
Duplicate gestures are now refused
Two rules that share the same gesture, modifiers, and scope are indistinguishable to Glimble — only the first one ever fires, so the second was a dead rule sitting in your list. Now:
- The rule editor names the rule that already owns a gesture and disables Save.
- Saving an existing rule onto another rule's gesture is refused too.
- Rule files that already contained duplicates are cleaned up on load. If a disabled rule was shadowing an enabled one, the enabled rule survives — that is the one that was actually firing.
Same gesture with different modifiers, or scoped to a different app, is still allowed: both are reachable.
New action: Media control
Map a gesture to Volume up / Volume down / Mute / Play·Pause / Next track / Previous track. Glimble synthesizes the same event the physical media keys emit, so macOS draws the volume HUD and transport keys reach whichever app owns Now Playing.
Brightness and fast-forward/rewind are deliberately not offered — they post without error but do nothing on modern macOS, so they would be dead actions.
Fixes
- An unreadable
rules.jsonused to be treated as "no rules" and overwritten with the defaults. It is now preserved asrules-unreadable-<timestamp>.jsoninstead.
Install
brew tap gum798/glimble
brew trust gum798/glimble
brew install --cask glimble
xattr -dr com.apple.quarantine "/Applications/Glimble.app"
Already installed? brew upgrade --cask glimble, or use Check for Updates… in the menu bar.