Up Arrow key cycles through Query history

[Garulf]

Similar to how arrow keys work in most shells this PR allows the user to press Up to cycle through their last used queries.

Todo:

• Cycle through entire history if user hasn't moved selection
• Fix not being able to move selection in History view
• Add custom hotkey support

2021-12-01.13-12-27.mp4

[onesounds]

• The same problem exists in the context menu.
• I think there should be a shortcut to erasing it. (ctrl+u?)

And do we really need this function? In my experience, the command line selects a re-input item by looking at the screen entered by itself. in this function, we have to guess and turn the record around. So there is a history list. From a modern command point of view, Using the command-like method is more of a modern commander, backstep to the past. If were me, I would simply add hotley (alt+up?) in history menu. or add setting history in first screen.

[jjw24]

i cant seem to cycle past the first history that showed, basically if i keep pressing up after the first history it just cycle through the results from it.

also need to check and not trigger when in context menu

is this pr still draft?

[Garulf]

i cant seem to cycle past the first history that showed, basically if i keep pressing up after the first history it just cycle through the results from it.

also need to check and not trigger when in context menu

is this pr still draft?

Yeah it's still just a proof-of-concept...

[Garulf]

output.mp4

Working

[Garulf]

Currently Alt+Up & Alt+Down Only trigger if defined in MainWindow.xaml and will not trigger from MainWindow.xaml.cs. Custom modifiers "work" but it's not the ideal solution to define them in both. Currently looking for a solution.

[Garulf]

i am getting this error. repro:

1. only one history result present
2. up arrow to insert the query
3. alt + down arrow to forward search

Fixed: c6d5525

[jjw24]

@Garulf this is ready for review again? (Merge Dev if so)

[Garulf]

Currently Alt+Up & Alt+Down Only trigger if defined in MainWindow.xaml and will not trigger from MainWindow.xaml.cs. Custom modifiers "work" but it's not the ideal solution to define them in both. Currently looking for a solution.

Could not find a good method to set Alt & Ctrl modifiers. Should I hard code it to Alt or keep as is?

Thoughts @Flow-Launcher/team ?

[jjw24]

The modifier hotkey can set Alt, does that part of the code offer any help?

[Garulf]

The modifier hotkey can set Alt, does that part of the code offer any help?

The problem is the current implementation requires the hotkey be coded in two separate files. Doesn't feel like a great fix.

[Garulf]

Removed from GUI for now

[taooceros]

close in favor of #2696