Sorry, yes, awkwardly looked through the code afterwards, and it seems to already have logic to begin a new search as soon as one hits Enter.
Then I remembered I'd changed the Find Next/Prev shortcuts to "Enter" and "Shift+Enter" shortly after installation. I reverted them to the original shortcuts (Ctrl+G etc.) and that latency is no longer noticeable.
I guess qpdfview is currently unable to disambiguate between "Enter" to begin a new search and "Enter" as "Find Next" -- therefore, choosing the latter every time? Do you think this is something that can be resolved, considering how Enter is a very common Find Next shortcut?
Sorry, yes, awkwardly looked through the code afterwards, and it seems to already have logic to begin a new search as soon as one hits Enter.
Then I remembered I'd changed the Find Next/Prev shortcuts to "Enter" and "Shift+Enter" shortly after installation. I reverted them to the original shortcuts (Ctrl+G etc.) and that latency is no longer noticeable.
I guess qpdfview is currently unable to disambiguate between "Enter" to begin a new search and "Enter" as "Find Next" -- therefore, choosing the latter every time? Do you think this is something that can be resolved, considering how Enter is a very common Find Next shortcut?