How exactly would this "quick help" work? A persistent result for each plugin that its enabled for, which when clicked, activates its keyword?

@cibere

How exactly would this "quick help" work? A persistent result for each plugin that its enabled for, which when clicked, activates its keyword?

If you click the enabling checkbox in the plugin's settings, its keyword appears in the quick help strip. The strip itself is only a static text display, visible any time FL's text entry field is visible, but with no interactive features of its own. I do not think it is necessary to allow clicking the keyword since FL is designed to keep your hands off the mouse.

It's basically like having a configurable post-it note that appears with FL.

The use cases are the new user, who summons FL but has not mastered all of the keywords... And the experienced user who has just added a plugin or two, to help them remember their new abilities.

Some users might value a minimal UI and turn off the quick help once they had memorized everything, others might like a constant reminder about less-used options. (That would be me.)

If you click the enabling checkbox in the plugin's settings, its keyword appears in the quick help strip. The strip itself is only a static text display, visible any time FL's text entry field is visible, but with no interactive features of its own. I do not think it is necessary to allow clicking the keyword since FL is designed to keep your hands off the mouse.

It's basically like having a configurable post-it note that appears with FL.

ah that makes more sense. I didn't noticed that top bar in your screenshot.

Similar request. #3123

think this is necessary. The approach you suggested is a bit complicated, so it won’t be in that form. The design proposed in #3123 has actually existed before, so it should be relatively easy to implement. (Although it wastes some space, it seems to be the fastest way to implement it.)

By enabling a specific setting, we can force the last query style to be empty and always display that list when Flow is opened. It would also be good to add a function key that shows the list while a specific shortcut key is held down and hides it when released.

Anyway, I’ll add this feature to the to-do list. (For now, I’m busy working on the transparent window, so I can’t do it right away.)

Similar request. #3123

think this is necessary. The approach you suggested is a bit complicated, so it won’t be in that form. The design proposed in #3123 has actually existed before, so it should be relatively easy to implement. (Although it wastes some space, it seems to be the fastest way to implement it.)

Yeah, that makes sense and it matches the look of the existing GUI. Cool. Glad it's on the list.

It would also be good to add a function key that shows the list while a specific shortcut key is held down and hides it when released.

Love it.

Thanks!

I was trying to implement this, but then I realized that the built-in plugin indicator already shows the list of keywords when using the ? keyword. (I had completely forgotten about that.) I think it would be better to just add a note suggesting users try the ? keyword, and functionally, the current setup seems sufficient. What do you guys think?

@onesounds

Cool, I didn't know about ? either.

What if by default, when no other input is available, ? is prefilled? It could even be prefilled and selected. This way, you can still scroll the list of hints, but you may also choose to type as with a blank input field.

There is an plan from the team called "home plug-in" function. (This is a plug-in triggered when nothing is entered.) If user set "plugin indicator" to home, it will work as you say. (Basically, every time you open the flow, you can see the entire keyword list) We will review this issue more in that direction.

p.s And even now, if you change the action keyword of this plug-in to * instead of a question mark, it works similarly. (When I tested it earlier, the order came out a little strange.)