| Summary: | F3 should "Find next", as in Konqueror | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | Daniel Naber <misc2006> |
| Component: | commands and actions | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | annma, bjoern, bluedzins, cyberbeat, olekgutjwr |
| Priority: | NOR | Keywords: | junior-jobs |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Daniel Naber
2003-02-19 17:21:40 UTC
Works for me with head. It doesn't work for me (HEAD). Here's what I do: the reader pane has focus, I type Ctrl-F and search for a string. I close the find dialog and press F3. Nothing happens, although there are more occurences of my search string. Doesn't work in version 1.9.1 (KDE 3.5). Reproduced with kde 3.5.1 It cannot work because there is no such feature as "find next". So how pressing F3 can help? I agree with this wish of course. works here in trunk perfectly. Can other people using a recent trunk build confirm that it works? Because I'd like to close this. Please, keep it open -- even if it works, this is obscure implementation. There is no such entry in Edit menu, nor in keyboard shortcuts. Compare this to Konqueror. Well, in KDE 4 pressing Ctl+F opens a searching pane. But F3 does not work after that. Before it works, you must click the searching pane to give the focus to it. After that, F3 works as expected. The searching pane should automatically get focus. This is about calling a setFocus() in the right place. I mark this as an junior job. a) what if there is no search pane -- "find next" means "find next", not "show search pane, focus, and then find next". The difference is important especially for small screens b) it is wrong for even with search pane shown because it is counterproductive (try kate with search pane opened and just imagine what happens when search pane gets focus each time user hits find next), Konqueror does not have caret mode yet (right?) but even with forms it would kill usability This feature request is still valid for KMail 2 Reassigning to product kmail2 maybe my bug 283586 is related |