[Feature] Dialog Jump: middle-click / double-click empty area to open jump UI (like Listary)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading the Dialog Jump implementation and how Flow Launcher detects mouse input and distinguishes Explorer from file dialogs; the issue does not name specific files or tests. Define the supported triggers and per-context settings, then verify that enabled gestures open the jump UI in the intended contexts and can be disabled to avoid conflicts.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Dialog Jump is useful, but it currently relies on the search hotkey / fixed bar under Open/Save dialogs. Listary and Direct Folders let users middle-click (or double-click empty area) inside Explorer / Open-Save dialogs to open a folder jump menu. That mouse gesture is faster when one hand is already on the mouse.
Describe the solution you'd like
Add optional mouse triggers for Dialog Jump:
- Middle-click in File Explorer / Open-Save dialog → show Dialog Jump (or a favorites/recent folders popup)
- Optionally: double-click empty area (Listary-style)
- Settings toggles to enable/disable these per context (Explorer, file dialog), to avoid conflicts with other tools
Describe alternatives you've considered
- Using Listary / Direct Folders alongside Flow (extra app, overlapping launcher features)
- Only using Alt+G / Dialog Jump hotkey (works, but less convenient for mouse-first workflow)
Additional context
- Flow Launcher version: 2.1.4
- Windows version: Windows 11
- Related: Dialog Jump feature; Listary "Mouse middle-click to show popup menu"
- Dominant language
- C#
- Stars
- 16k
- Forks
- 673
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 9
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Flow-Launcher/Flow.Launcher
-
bug keep-fresh
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Flow-Launcher/Flow.Launcher#4744 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Flow-Launcher/Flow.Launcher#4660 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement keep-fresh kind/ux
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Flow-Launcher/Flow.Launcher#4743 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Flow-Launcher/Flow.Launcher#4736 · 1 comment ·
Maintainers usually reply within 1 day
-
issueOpen
Difficulty 3/5 Half a day Newbie friendliness 40/100
Flow-Launcher/Flow.Launcher#4735 · 1 comment ·
Maintainers usually reply within 1 day
All issues in Flow-Launcher/Flow.Launcher
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Facepunch/sbox-public#12305 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
JiaFeiMiao-K-Cat/DiscImageStudio#205 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
flyingpie/windows-terminal-quake#419 ·
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
a-corriger documentation
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
christian-raj/S-Aloha#272 ·