| Summary: | [find/replace] Upon search wrapping, indicate to user search has indeed wrapped | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Sean McRae <smcrae> |
| Component: | Text | Assignee: | Platform-Text-Inbox <platform-text-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P5 | CC: | daniel_megert, esycat, markus.kell.r |
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
|
Description
Sean McRae
I assume this bug report is about the editor's Find/Replace command and not about the Search (e.g. Search for declarations) component. Fixed in builds > I20030924 Was it a deliberate decision to *only* beep on wrap? I would appreciate a short
message in the StatusLine as well ("Search wrapped around").
This is a help for visually oriented people, people working in a nosy
environment, or people confused by the sudden beep and looking for an explanation.
We could also provide visual indication. The beep is there for Edit > Find Next / Previous, but not when I press the Find or the Replace/Find button in the Find/Replace dialog. I get the beep in both cases when it wraps. What I don't get is the beep when nothing more is found and wrap is off. It now also beeps when the end is reached in non-wrap mode. The problem reported in comment 5 can be reproduced if 'Incremental' is checked. I've fixed this too. We won't work on the visual indication when wrapping. We should just fix this accessibility issue and provide a status bar message when search wrapped (via dialog and via shortcuts). Incremental find already does that. Fixed in HEAD (> 3.6 M4) for the dialog. Fixing it for the Find Next/Previous action is hard because the post-selection event clears the status message again. The remaining issue is not an accessibility problem. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag. |