Community
Participate
Working Groups
If member function but not the class itself are categorized then hiding "Uncategorized Elements" does not show any elements. Proposed solution: The categorie entries shuld be made the root elements or all parent nodes of catgeorized nodes should be shown even if they are not categorized.
The following source produces outline views as shown in the attachment. public class A { /** @category One */ public void methodOne() {} } One can see that a category for the class would be necessary to enable hiding of the uncategorized members.
Created attachment 47681 [details] Illustration of the situation.
Same problem when you have: /** @category Two */ public class A { /** @category One */ public void methodOne() {} } and hide 'Two'. This works properly: The member A his hidden (and therefore all its children of course). Not hiding it would be a bug, unless we say, that an element implicitly inherits all categories from its children, but I don't think this is the semantic chosen for categories. Closing as wont fix, Dani, reopen if you don't agree.
Categories are normally used to split members of a type into several groups. It rarely makes sense to make the declaring type a member of all categories. See e.g. IJavaSearchConstants. It's also hard to explain why categorized members are shown only when "Go Into Top Level Type" is checked.
(In reply to comment #4) > Categories are normally used to split members of a type into several groups. It > rarely makes sense to make the declaring type a member of all categories. See > e.g. IJavaSearchConstants. +1 Thinking more about it in the context of bug 202490, I was about to request a reopen myself, but Markus was faster than I ;-)
>Proposed solution: The categorie entries shuld be made the root elements See bug 132326.
With colored labels we can now use i.e. gray for elements which do not belong to a selected category but contain children which belong to one of the selected categories.
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.
