Add input box input anti-shake function

[lukxu]

Is your feature request related to a problem? Please describe.

Each time a character is entered in the input box, the program will be executed once

Describe the solution you'd like

My idea is to add an anti-shake function to the input box, and then trigger the execution of the program after the input is completed, instead of triggering the execution of the program every time a character is entered.

For example, if a character is input again within n milliseconds after each input of a character, the execution of the program will not be triggered, and if no more characters are input after n milliseconds, the corresponding program will be executed

This feature can be set as an optional feature if implemented.

[jjw24]

Hey how's it going?

Currently it is not too big of a cost speed wise to execute when a character is entered. What is the root problem you are looking to solve?

[Garulf]

Hey how's it going?

Currently it is not too big of a cost speed wise to execute when a character is entered. What is the root problem you are looking to solve?

I believe he's suggesting the opposite. He'd like a delay between characters entered before Flow attempts to compute the query.

[jjw24]

Yeah but I am trying to explore the root issue that @qjcXu is looking to solve.

[lukxu]

Hey how's it going?

Currently it is not too big of a cost speed wise to execute when a character is entered. What is the root problem you are looking to solve?

For example, the function of a plug-in is to request an interface to return the corresponding content.

When I input the 4 characters of flow in sequence, if I don’t add the input anti-shake, there will be an extra 3 program executions, but this is Not necessary, because my purpose character is flow, not f fl flo.

[Garulf]

Alfred has a similar function that waits for user input to stop for a predetermined amount of time before execution of results.

[lukxu]

Alfred has a similar function that waits for user input to stop for a predetermined amount of time before execution of results.

Yeah, similar to this function

[jjw24]

Is this feature to help with your plugin @qjcXu ? If so what's the issue currently?

[lukxu]

Is this feature to help with your plugin @qjcXu ? If so what's the issue currently?

My plugin is to request interface and return data

For example, the user's purpose is to get the translation result of flow, but it will send three extra requests f fl flo , these three requests are unnecessary.

[jjw24]

Aside from the request being unnecessary, it doesn't really impact user experience though right?

[lukxu]

Aside from the request being unnecessary, it doesn't really impact user experience though right?

I just updated my plugin to fix this, but inevitably, the user has to wait a certain amount of time before requesting the interface again.

I think it still affects the user experience a bit.

[jjw24]

What's the impact though letting the plugin just make those requests?

@Garulf how do your plugins that need to make API requests handle this? I would imagine they also make requests per keystroke too?

[deefrawley]

I too don't understand the problem this would solve. The results are very fast so why can't you handle rate limiting or response in your plugin @qjcXu ?

[lukxu]

I too don't understand the problem this would solve. The results are very fast so why can't you handle rate limiting or response in your plugin @qjcXu ?

In my latest released version I solved this problem.

I found that the logic of the launcher to start the plugin is to trigger a new execution of the plugin every time a character is entered, so my solution is to determine whether the current is continuous input only by storing the start time of the last plugin, but this is very affect the user experience.

If you add the input anti-shake function to the input box of the launcher, this can record whether the current input is continuous, and the experience will be better.

[taooceros]

I do have added an anti-shake function very long ago. However, it is a very short interval (40ms) to accommodate debug experience and backspace. I feel like it's more reasonable for plugin to have their own antishake function because sometimes we have some plugin that users would like to get response as soon as possible (calculator, etc.).