[okular] [Bug 355467] Find from current page does not work for successive finds.
https://bugs.kde.org/show_bug.cgi?id=355467 --- Comment #6 from orionbe...@gmail.com --- Right, and also hitting Esc a second time is not obvious either, unless you do it by accident. Even if the previous search result is still in view and you see it disappear when (by accident) you hit Esc a second time, i think the notion that this cancels the previous search is not entirely obvious, even less so the notion that this resets the current page in case of a new search... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 355467] Find from current page does not work for successive finds.
https://bugs.kde.org/show_bug.cgi?id=355467 --- Comment #5 from Albert Astals Cid --- Hitting esc cancels the serach so the last highlighted result goes away, i agree this is "non obvious" if it's out of your view though -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 355467] Find from current page does not work for successive finds.
https://bugs.kde.org/show_bug.cgi?id=355467 --- Comment #4 from orionbe...@gmail.com --- Thanks a lot for the answer. Indeed, the key is hitting Esc twice to cancel the current search. Is this something obvious that i just happened to ignore or is it something that should be documented somewhere? I looked into the okular handbook and web site and i failed to find any mention that hitting Esc twice cancels the current search. A more visible way to make it obvious might be to add a "cancel search" option somewhere (in the menu bar, where the shortcut would also be mentioned, or in the search bar at the bottom). Hitting Esc once has an obvious and visible effect in the various contexts where it is applicable. But the double-Esc thing is not at all obvious, and i am now wondering whether i also miss other uses of it in different contexts. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 355467] Find from current page does not work for successive finds.
https://bugs.kde.org/show_bug.cgi?id=355467 Albert Astals Cid changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from Albert Astals Cid --- You just type the new word you want to search. If you want to search the same word you were searching, you press Esc twice (first closes the search bar, second cancels the existing search) and then search again. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 355467] Find from current page does not work for successive finds.
https://bugs.kde.org/show_bug.cgi?id=355467 orionbe...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 355467] Find from current page does not work for successive finds.
https://bugs.kde.org/show_bug.cgi?id=355467 orionbe...@gmail.com changed: What|Removed |Added CC||orionbe...@gmail.com --- Comment #2 from orionbe...@gmail.com --- So how does one try a new search? The scenario is the following: 1. I run a search with "from current page" enabled. Okular correctly finds the next match (in or after the current page). 2. I then move to another page in the document. 3. I now want to run a search from *that* new page down. Whether i have "from current page" checked or not, Okular continues searching from the last location it was in step 1. So how do i do what i want in step 3? Thanks. -- You are receiving this mail because: You are watching all bug changes.
