When you want to search for text, for example in the “direct to” function, the search is triggered at every keystroke and the keyboard stays locked while waiting for the search to return.
So when you’ve typed two letters the keyboard is frozen — you can’t continue typing, then the result appears, then you can type the third, then wait, then the result, then you can finally type the 4th, and so on..
You can type letters in advance into the buffer but you’re never sure whether you actually typed the letter or not since they don’t display in real time.
If you have the misfortune of typing it a second time like “nurennbberg” obviously you have to start all over
As a result it takes a lot of time.
Would it be possible to allow entering the text first, and then have a button to launch the search? “Nurenb” enter.
that shouldn’t be happening. Could you tell me which device you’re using? The results shouldn’t affect your typing. That’s intended and it’s the same on my test devices. I’ll fix this issue in the upcoming update Thanks for the heads-up!
,
Thanks for the heads-up!