Slight delay pattern for roSearchScreen?
Hello, Total newbie here, guys! Can anyone think of a pattern that would let me delay execution for a little while after a user has entered a character on roSearchScreen? If I were at my day ...
Forum Discussion
I typically use a very low wait time (250ms), record the isPartialResult() in a variable, then act on that partial result on the next "invalid" event. That essentially introduces a 250ms delay between the last letter selection and calling out to the API, and allows for letters entered in rapid succession to stack instead of queuing up for multiple API queries (i.e., one api.Search() call for "test" instead of four for "t", "te", "tes", and "test"). You could adjust that wait time up or down depending on your preference for delay.
