https://bugs.documentfoundation.org/show_bug.cgi?id=47122
Justin L <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|non-dialog searching: |non-dialog searching: |missing .uno |desirable to have .uno |FN_REPEAT_REVERSE_SEARCH |FN_SEARCH_FORWARD and |keyboard shortcut - only |FN_SEARCH_BACKWARD keyboard |have FN_REPEAT_SEARCH |shortcuts (comment 10) |(comment 9) | --- Comment #11 from Justin L <[email protected]> --- (In reply to Hossein from comment #10) > Bug tdf#142219 also provides some good points: the problem is > "inconsistency" in find-next and find-backward shortcuts. Technically there can't be any inconsistency here because in-document searching doesn't do either of those - it just does repeat search - a capability that the find toolbar doesn't even have. > This is the expected behavior, having two shortcuts for forward and reverse > search. Sure, that is reasonable to instead add two UNO commands that are explicitly directional. > One issue that I see is the collision with Ctrl+G for "Edit > Go to Page". > This is also happening for F3, for "Run AutoText Entry". IMO, re-using > shortcuts in this way is a bad idea. See bug 70001 comment 6 where this is addressed. In both cases we match what MS Word does. Generally speaking - matching MS Word is a good idea. So all of this discussion basically makes this not an easy-hack anymore. The easy-hack aspect would be to create the UNO commands and make them available for people to attach their own keyboard shortcuts to. IMHO neither of these two new commands should have default keyboard assignments. -- You are receiving this mail because: You are the assignee for the bug.
