BUG: Pressing "Enter" before search delay ends doesn't do anything

[Meteony]

Checks

• I have checked that this issue has not already been reported.

• I am using the latest version of Flow Launcher.

• I am using the prerelease version of Flow Launcher.

Problem Description

E.g. for some action keywords I can already predict the first match without having to see the results.
In practice however if I hit enter too soon, Flow doesn't perform a search at all leading to no actions executed.

To Reproduce

1. Type a short query fast (~200ms)
2. Hit enter
3. Literally nothing

Screenshots

No response

Flow Launcher Version

Release

Windows Build Number

Microsoft Windows [Version 10.0.26100.7171]

Error Log

Details

Replace this line with the important log contents.

[deefrawley]

Are you using the latest version?

[Meteony]

Are you using the latest version?

Yes

[Jack251970]

Before search delay, the search function of plugins are not called so Flow cannot get the results to execute their click actions.

[Meteony]

Before search delay, the search function of plugins are not called so Flow cannot get the results to execute their click actions.

Well I think it'd be more logical to advance that function call to whenever Enter key is pressed in cases where the delay is still in effect though

[deefrawley]

200ms is not a realistic use case. I think we should close this.

[Jack251970]

Before search delay, the search function of plugins are not called so Flow cannot get the results to execute their click actions.

Well I think it'd be more logical to advance that function call to whenever Enter key is pressed in cases where the delay is still in effect though

Actually, search delay is designed to mitigate possible memory issue with instant calls of search functions and improve display effect for dense character input. So I think this situation is just normal.

If you would like to execute results for some plugins, please just set their search delay to 0ms.

[Meteony]

200ms is not a realistic use case. I think we should close this.

I have always left it at 200ms on my laptop because there are quite a handful of plugins that really stutter when performing a search (dictionaries etc) and setting the delay to 200ms ensures that no searches will be done until I'm 100% done typing out the query.

There's definitely a use case for this and I don't necessarily think that I'm alone in having it that way to be honest

[Meteony]

Before search delay, the search function of plugins are not called so Flow cannot get the results to execute their click actions.

Well I think it'd be more logical to advance that function call to whenever Enter key is pressed in cases where the delay is still in effect though

Actually, search delay is designed to mitigate possible memory issue with instant calls of search functions and improve display effect for dense character input. So I think this situation is just normal.

If you would like to execute results for some plugins, please just set their search delay to 0ms.

I use it to mitigate the lags caused by certain plugins that perform really resource-intensive searches.

Don't know if my description meshes with your intended use case; I do end up finding it really useful for that.

Didn’t know it was possible to set custom query delays. It indeed helps a lot

[Jack251970]

@Meteony Since we can set some plugins to have no delay so that their results will pop up instantly, I wonder if we can close this as complete?

[Meteony]

@Meteony Since we can set some plugins to have no delay so that their results will pop up instantly, I wonder if we can close this as complete?

Sure