Community
Participate
Working Groups
Build ID: M20090211-1700 Feature Request: I continually open these two dialogs and type my search string before realizing that I've opened the wrong one. It would be great if I could press Ctrl-Shift-T/Ctrl-Shift-R and have it switch between the two search dialogs taking the current search string with it.
Interesting idea, especially in the light of other Open xyz dialogs (e.g. CDT).
The obvious solution would be to only have one dialog, Open Resource (Ctrl+Shift+R). What would we have to do to the Open Resource dialog so that you would not miss Open Type?
>What would we have to do to the Open Resource dialog so that >you would not miss Open Type? It should be possible to go directly to the 'Open Type' page with Ctrl+Shift+T and then allow to switch to another page either like in the Search dialog or via combo or via key binding (e.g. Ctrl+Shift+R).
Note that the patterns supported by Open Resource and Open Type are not the same, so I wouldn't try to merge the result sets. But I agree that in-place switching would be handy for simple patterns. Differences in the patterns are e.g. that Open Type supports Java package prefixes, while Open Resource should support directory paths (bug 86973).
Switching could also switch the input field along with the pattern rules. CDT might yet have more/other rules than JDT.
*** Bug 349143 has been marked as a duplicate of this bug. ***
When I used IDEA for a time I found the ability to switch from Ctrl-N to Ctrl-Shift-N (and vice versa) a really nice feature. The neat part is that the search text is retained. I certainly don't think these two dialogs should be merged, but this would be a great enhancement to improve the UX.
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.
Issue is still relevant.
11 years after opening, this is the kind of minor, quality-of-life UX improvement that just never makes it into Eclipse :(
