Community
Participate
Working Groups
Build Identifier: Hello , I m looking for an enhancement in eclipse particularly in Java Perspective which makes Development easy . When we Press the Ctrl+shift+T Key eclipse will provide option to Search a Class which is Default behavior. I m looking for change to include search for the Inner Class or Interface on pressing Ctrl+shift+T Key . For Example Let say java.util.Map Interface having "Entry" Interface inside that. When we type Map.Entry in search box eclipse should take directly to the Map$Entry file. Please Let me know any clarification on my Question. Thanks Kathir Reproducible: Always Steps to Reproduce: Press the Ctrl+shift+T Key
You need to search for "*Map.Entry" in the Open type dialog to get to an inner type. (I mentioned this in another reply on the newsgroup, but maybe you did not see that). Internally we add a trailing * (or something equivalent) to the search pattern entered in the dialog. e.g. searching for 'TextEditor' returns 'TextEditorAction', 'TextEditorAdapter' etc. Is there a good reason why we do not automatically add a leading * as well ? (If we do anything here we should also do it in other places e.g QuickOutline)
>Is there a good reason why we do not automatically add a leading * as well ? Because the result is less precise. Why not simply type "Entry"? Having said that, searching for "Map.Entry" finds the interface, so Open Type should probably behave the same.
More precisely, you should search for "*.Map.Entry", otherwise you'd also get matches like "java.util.LinkedHashMap.Entry". This actually shows nicely why automatically adding a "*" at the beginning would be a bad idea. > Having said that, searching for "Map.Entry" finds the interface, so Open Type > should probably behave the same. I agree.
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. -- The automated Eclipse Genie.
Comment 3 is not implemented/fixed as of 4.14.
