Add "override" option to conflictbehavior.

[JarvisH]

When dealing with certain hotkeys, which essentially do the same just in different contexts, it becomes difficult to manage which should have priority.

Example: opening a modal from different contexts or components, where the hotkey callbacks differ slightly. This currently forces a tight coupling between components where one needs to know the current active state of the other.

I am unsure if this idea goes against conventions, but it could be nice to have an override option as conflict behavior, i.e. temporarily disabling all previous hotkey registrations.

[JarvisH]

The more I think about it a better approach would probably be an option to temporarily reset all current hotkey registrations.

One use-case would be this:

• Component A registers hotkey Mod+C and mounts Component B
• B may or may not need to register its own Mod+C hotkey.
• While B is active the hotkey in A should not trigger.

This becomes cumbersome to manage as Component A suddenly has to track if any other relevant component is rendered.

A solution could be:

• Allow a boolean persistent or similar option to a registration.
• Add a composable to handle reset on mount and re-registration on unmount.

// Component A
useHotkey('Mod+A', callbackA, { persistent: false )

// Component B
useResetHotkeys()
useHotkey('Mod+A', callbackB, { persistent: false )

// rudimentary useDeactivateHotkeys composable
const useDeactivateHotkeys = () => {
    const mgr = getHotkeyManager()
    
    // temporarily deactivate or create
    // backup of all current registrations
    // if they are not marked as "persistent"
    mgr.deactivateCurrentRegistrations()

    onUnmounted(() => {
        mgr.reactivateRegistrations()
    })
}

One edge-case to handle would be certain hotkeys which may need to be persistent except in a few cases, e.g. a global search dialog. For this case a boolean argument may be needed:

const forceDeactivation = true
mgr.deactivateCurrentRegistrations(forceDeactivation)

[JarvisH]

I am closing this discussion, as scoped hotkey targets are better suited to handle this.