FNSTools by Function Store

Docs Interface

HotkeyManager

Unified hotkey discovery, conflict detection and rebinding UI across the whole toolkit.

▦ Interface Hub tab

HotkeyManager

A lister UI for discovering, rebinding and de-conflicting hotkeys across the whole project, including tools outside the toolkit. Pulse Open UI on the component to open it.

  • Discovery scans every top-level component (except ui/sys/local) for hotkey-bearing keyboardin CHOPs/DATs and custom parameters named like a shortcut, and lists them one row per binding: Tool, Path, Par, Hotkey, Default, Persist, Status.
  • Click a Hotkey cell to capture a new binding (press the keys; Esc cancels). If the combo is already used elsewhere, the row asks for confirmation; press the same keys again to force it.
  • Right-click a Hotkey cell to reset that binding to its default.
  • Conflicts (the same combo bound by more than one tool) are flagged in the Status column; clicking a conflicted row's status jumps to (and cycles through) the other row(s) sharing that combo.
  • Persist column: toolkit hotkeys always persist. A hotkey outside the toolkit only persists across projects/updates if declared: tag its keyboardin (or a COMP containing it) FNS_hotkeys, or use the Persist cell to toggle it. Declared bindings are externalized into your user palette via ConfigRegistry and restored on load; project-local bindings never persist.
  • Save/Load/Load Default pulses (and a Force Default toggle) are also exposed as the component's own custom parameters.

Get it

Tick it on the install page and it installs with the rest of your setup and stays up to date.

Download FNS_HotkeyManager.tox Version 3.2.8, the tool on its own. It works in any project, and this copy never updates itself.

Where it appears

Parameters

Its Registry page comes from FNS_ConfigRegistry and FNS_HubRegistry.

Custom

ControlType / defaultWhat it does
ActiveActive on / offon Turn hotkey management on or off. Off leaves every binding as it is but stops the manager applying, saving or restoring them.
Save HotkeysSavehotkeys button Write the declared bindings to your user palette now, so they survive project files and updates. Toolkit hotkeys are always declared; anything else has to be tagged FNS_hotkeys or ticked in the lister's Persist column.
Load HotkeysLoadhotkeys button Re-apply the saved bindings from your user palette over what is bound right now.
Load DefaultLoaddefault button Put every discovered binding back to the default its own parameter declares, discarding your saved bindings for this session.
Force DefaultForcedefault on / offoff Ignore saved bindings entirely and use each parameter's declared default on every load. Use it to get a machine back to a known state; leave it off to keep your own bindings.
Excluded RootsExcluderoots textui sys local Space-separated names of top-level components to SKIP during project-wide hotkey discovery. TD's own ui/sys/local are excluded by default; add other roots here to silence them.
Open Hotkey UIOpenui button Open the hotkey configurator panel: every discovered binding grouped by tool, click a Hotkey cell to rebind via key capture, right-click to reset to default. Conflicts are flagged in the Status column.

Edit this page on GitHub →