Data Picker Observation - Poss. Improvement

[bpj]

I have quite a complex project that has a lot of elements (probably could be tidied) and have noticed the search time for the data picker slowing down dramatically. I have seen posts by others who have experienced this too.

What I have noticed is that when copy and pasting an id into the search, the result appears almost instantly. What it looks like is that it is starting a search on every key press. When each search takes a few seconds and you type several letters, it seems to be adding quite an overhead.

Just hoped that spotting this might help refine that element of the UI.

[scott]

If I remember reading correctly, the search starts looking once something is inputed into the search field. So when you paste something in, the search would be instant because the complete word or phrase being entered was pasted. In contrast, when you type something in manually, the search starts looking when the first character is entered and then starts over when the second character is entered, etc.

I believe that the solution was something to do with debounce (although I have not used it personally).

Here is one of the topics that discusses it. While not exactly on point, it discusses how to use debounce to delay a server connect response based on time.

Using Shortcut Keys for Dynamic Events

With Wappler you can assign different Keyboard Keys as shortcuts for different dynamic events, like: controlling a slideshow, run server action, refresh data, update record, show modal etc. We will show you how to assign shortcut keys for controlling the Swiper component. Select App in the App Structure(1) and add new Dynamic Event (2): [Screenshot_7] Then in the Keyboard group select on Key Down: [Screenshot_8] And click the dynamic action button, to select what to happen on key down: […

[bpj]

Thanks @scott, I appreciate the response.
This is the search in the Data Picker in the Wappler UI, not on a page, that I’m talking about. It will be @george/the Wappler team that have to add a debounce to the program to solve it.

[scott]

Hey there @bpj, sorry I misunderstood what you meant.

I see George has already been assigned to look into this, but for my understanding, would you be willing to post a screenshot of what part of the UI you are referring to?

It may be a part of Wappler that I have never used.

[bpj]

Hi @George,
I hope you had a good break. Could I give this a gentle bump please?

[bpj]

Thanks @george

[George]

Implemented in Wappler 3.7.0