Skip to content

v2.5.0

Choose a tag to compare

@crftwr crftwr released this 14 Oct 23:31
· 381 commits to main since this release

Keyhac 2.5.0

Two things move under an existing configuration. Your key tables now
apply inside the chooser.
Until now the chooser's keyboard grab bypassed
them, so a global remap — say Ctrl-H to Back, or Emacs-style cursor keys —
stopped working the moment a chooser opened. Now the chooser is matched as if
it were the focused window (app Keyhac, title Chooser), and a binding's
output goes to the chooser rather than the application underneath. If a global
binding of yours takes a key the chooser itself relies on, the binding now
wins; give the chooser its own table with
keymap.define_keytable(app="Keyhac", title="Chooser") to put it back.
And keymap.pop_balloon() from your config now appears where you are
typing
, not in the top-right corner of the first screen. Pass
anchor="corner" to keep the old placement, or anchor="window" to place it
against the focused window.

  • Key bindings work inside the chooser. Remaps, functions, multi-stroke
    prefixes and user modifiers all apply while a chooser is open; only keys no
    table binds reach the chooser's own handling. keymap.focus, window actions,
    IME and MCP still see the real focus, and a chooser bound only in an
    app-specific table still toggles.
  • Windows can be maximized, put in full screen, and restored. The
    isMaximized() / maximize() of Keyhac for Windows were lost in the port,
    and snapping a maximized or full-screen window did nothing visible. Windows
    now have maximize(), enter_full_screen(), is_maximized() and
    is_full_screen(), with restore() as the one way out of any of them. At
    most one state reports true, and every verb returns False when there was
    nothing to do. On macOS maximize() uses Window > Fill. Moving or snapping a
    maximized window, or one Windows snapped itself with Win+arrow, now takes it
    out of that state first, so it lands where you asked.
  • Keys no longer go dead after Ctrl+Alt+Del, a UAC prompt or the lock screen
    (Windows).
    Those screens run on a secure desktop the key hook cannot see.
    Keyhac saw a modifier go down but never saw it come up, so every key afterwards
    was read as a chord with a modifier nobody was pressing, and only a reload
    fixed it. Keyhac now notices the switch and resets its modifier state on the
    way out and on the way back.
  • Balloons appear near the caret on every monitor. A balloon popped from
    config.py had no anchor and fell to the top-right of the first screen, which
    on a multi-monitor setup is often a screen you are not looking at. Every
    balloon now follows the caret → focused control → focused window chain the
    multi-stroke help always used. An explicit near= / over= still wins, and
    the new anchor= argument ("window", "corner") names the exceptions.
  • MCP clients that ignore tool-list updates see the real tools. With the AI
    Integration switch off, the bridge used to offer a single placeholder tool and
    rely on a list-changed notification to swap in the real list. Clients that
    ignore that notification, such as Amazon Quick, kept the placeholder until
    restarted. The bridge now offers the same tool list whether the switch is on
    or off, and a call made while it is off returns the explanation as its result.

Also: the project site now has a link-preview image for chat and social
services.

Full Changelog: v2.4.2...v2.5.0