Summary: | [QuickAccess] Improve handling of duplicates or ambiguous matches | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Missing name <soloturn> |
Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | b.muskalla |
Version: | 3.4.1 | Keywords: | helpwanted |
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Missing name
2008-11-26 15:35:46 EST
is an ui issue ... Have you ever tried Ctrl+3 ? I think it's exactly what you're searching for. uh - you are right. how is it expected to work? 1. entries are missing. i have a plugin "mercurialeclipse", a gui for the mercurial source code control. the right button menu on a mercurial managed project contains "team", with "pull" as submenu. but pressing ctrl-3, typing team does not show a "pull". the same happens when typing "perspective". no perspectvie is offered to choose. 2. it contains double entries. typing "reset pers" brings up reset perspective two times, one time as command, one time as menu. both open the same thing. doing it another time shows it 3 times: last, command, menu. 3. its ambiguous typing "update" lists 2 entries called "update". on is for mylin tasks, the other (i guess) is the package explorer. 4. switch off complex menu, button bar not obious how could one set with a keystroke or choosing a menu entry a "simple" view, with no menu I'll pass this along as a QuickAccess bug but having the search work at this deep a level would be -very- difficult if not impossible (we may not have access to all the commands added by a specific plugin). BTW, I've changed the Severity to 'enhancement' to more closely describe what you're asking for... Unfortunately, we don't have the time right now to look at this. Patches would be welcome (see http://wiki.eclipse.org/Platform_UI/How_to_Contribute). Remy is now responsible for watching bugs in the [QuickAccess] component area. 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. |