Quick Access not working

[jjw24]

Repro: Go to context menu on a Window Walker result, select quick access and assign a '1' to it. Use Shortcut hotkey to list windows, no entries show except for the quick access result.

Expected to see a list of results including the assigned quick access result with '1-' appended to the title.

[13eel]

I think that I am experiencing the same issue, unless I haven't understood how to use an assigned quick access keyword once set

[echaya]

anyone figured out how to activate "quick access" mode that can trigger window by the key assigned?

[mykael90]

Title: Bug Report: Window Walker (v3.0.3) fails to save Quick Access Keywords

Body:

Hello Flow Launcher Team,

I'm reporting a persistent bug with the Window Walker plugin where the "Quick Access Keyword" feature is not functional. Assigning a keyword appears to work in the UI, but the keyword is never actually saved.

System Details:

• Flow Launcher Version: 1.20.1
• Window Walker Version: 3.0.3
• OS Version: Windows 11 (Build 26100.4349)

---

Steps to Reproduce:

1. Ensure the Window Walker plugin is installed.
2. Make any application window (e.g., Notepad) the active window.
3. Press the hotkey to assign a Quick Access Keyword (default Ctrl + Alt + D).
4. The Flow Launcher query box appears as expected.
5. Type a keyword (e.g., "testnote") and press Enter.

Expected Behavior:

• The keyword "testnote" is now associated with the Notepad window.
• Typing "testnote" into Flow Launcher should display the linked window as a result.
• The keyword and its associated window should be saved in the file located at: %APPDATA%\FlowLauncher\Settings\Plugins\Flow.Plugin.WindowWalker\QuickAccessKeywords.json.

Actual Behavior:

• After pressing Enter, the keyword is not saved.
• Searching for the keyword "testnote" yields no results from Window Walker.
• The file QuickAccessKeywords.json is never created by the plugin in its settings directory. The folder remains with only the Settings.json file.

---

Exhaustive Troubleshooting Steps Performed:

I have tried a comprehensive list of solutions with no success, confirming this is likely a code-level bug rather than a configuration issue:

• Run as Administrator: Ran Flow Launcher with elevated privileges. The issue persists.
• Hotkey Conflict Check: Changed the default hotkey to a different combination (Ctrl + Alt + F12) to rule out system-wide conflicts. The issue persists.
• Plugin Reinstallation: Completely uninstalled (pm uninstall Window Walker) and reinstalled the plugin. The issue persists.
• Manual File Creation: Manually created an empty QuickAccessKeywords.json file (containing {}) in the plugin's settings directory (%APPDATA%\FlowLauncher\Settings\Plugins\Flow.Plugin.WindowWalker\). After attempting to assign a keyword, the file remains empty and is not modified by the plugin.
• Fullscreen Mode Check: Tested the feature on non-maximized, floating windows to rule out interference from the "IgnoreHotkeysOnFullscreen": true setting. The issue persists.
• Log File Analysis: Checked the startup logs. The logs show that the Window Walker plugin initializes successfully (INFO - PluginManager.InitializePluginsAsync - Total init cost for <Window Walker> is...) without any errors. This indicates the failure happens silently during the keyword-saving logic itself.

Given that the plugin loads correctly but fails silently to perform its function, and that manually creating the target configuration file does not solve the problem, this strongly points to a bug within the plugin's code.

Thank you for your hard work and for looking into this issue.