Skip to content

BetterCmdTab 26.7-beta.3

Pre-release
Pre-release

Choose a tag to compare

View all tags
@rokartur rokartur released this 23 Jul 17:55
26.7-beta.3
f1e10bc

Highlights

This update adds a live config file and a cap on expanded browser-tab rows, and fixes a batch of input and display issues — non-US layouts for search and peek, wrong-chord direct activation, the switcher vanishing on other Spaces, and stale frames after occlusion.

Added

  • Configure the app through a plain-text config file at ~/.config/bettercmdtab/config.json ($XDG_CONFIG_HOME honored): create it from the new Configuration file row in Settings, edits to the file apply live while the app runs, and changes made in the GUI are written back so the file never goes stale (#117).
  • Cap how many tab rows an expanded browser window shows in the switcher with the new tab-row limit setting (#144).

Changed

  • Settings now export as flat, human-editable JSON (.json) — the same format the config file uses; importing older .cmdtab backups still works.

Fixed

  • Pressing a bound action key (like close window) with type-to-search enabled now performs the action instead of typing it into a new search query; unbound letters still start a search.
  • Fuzzy search (/) and tab peek (\) now respond on layouts where those characters need Shift or Option (e.g. French AZERTY), and the search field accepts Shift/Option characters so digits can be typed into the query (#141).
  • Fixed the switcher staying invisible on every other Space after quitting a full-screen app (#46).
  • Fixed direct-activation shortcuts firing on the wrong chord, such as an ⌥-digit press triggering a ⌃-digit slot on the French – PC layout (#120).
  • The browser tab access button in Settings is now "Check access…" and always answers with a result — which browsers are reachable, none running, or access declined with a shortcut to System Settings → Automation (#147).
  • Fixed the settings window (and a long-hidden switcher) briefly showing a stale, see-through frame when coming back into view (#146).
  • Fixed a failed background update check retrying in a rapid loop instead of waiting for the next scheduled check.

Full changelog: 26.7-beta.2...26.7-beta.3

Assets 6
Loading