Shun
状元
Hello Mike,
on an iPad running the .17 beta and using a 900,000-card flashcard database, I noticed that the handwriting input interface in Search sometimes reacted to my input only with a delay of three or more seconds, probably because it continually searched for dictionary definitions of the current input field, including all of my flashcards.
Would it perhaps be doable to decouple the search input from the searching for definitions and put these tasks into separate threads? At the moment, the dictionary search seems to halt the handwriting input, which indicates to me that they're waiting for each other. I think it would be nice to place whatever is input into a queue, with the searching happening in a different background thread which reads from the queue whenever it's ready for additional input. Intermediate inputs could then also be skipped (only the last contents of the user input field would count). This should make user input feel very responsive. The difference should also be noticeable with just 100,000 cards on an older device, though I'd have to experiment.
I left searching inside flashcards at the default setting. In the attached screen recording, I tapped on the character 间 on the left side multiple times before my tapping input was processed.
Thanks, Shun
on an iPad running the .17 beta and using a 900,000-card flashcard database, I noticed that the handwriting input interface in Search sometimes reacted to my input only with a delay of three or more seconds, probably because it continually searched for dictionary definitions of the current input field, including all of my flashcards.
Would it perhaps be doable to decouple the search input from the searching for definitions and put these tasks into separate threads? At the moment, the dictionary search seems to halt the handwriting input, which indicates to me that they're waiting for each other. I think it would be nice to place whatever is input into a queue, with the searching happening in a different background thread which reads from the queue whenever it's ready for additional input. Intermediate inputs could then also be skipped (only the last contents of the user input field would count). This should make user input feel very responsive. The difference should also be noticeable with just 100,000 cards on an older device, though I'd have to experiment.
I left searching inside flashcards at the default setting. In the attached screen recording, I tapped on the character 间 on the left side multiple times before my tapping input was processed.
Thanks, Shun
Last edited:
