When a family is created, there are some instances where subcategories either can't be assigned (annotative items, such as text and symbols), or where they don't sink properly (generic family subcategories inserted into a specific category family). When these instances happen, you're left with what I call "ghosts", or leftovers that cannot be turned off in the project without turning off the whole category. The only other way around this is to either manually find and hide every family with this problem (which doesn't take into account any added at a later time), or setting up a filter, which I always treat like a last-ditch effort.
The preferred solution would be for nested families to properly carry over subcategories, and for annotative items to be able to be subcategorized (why isn't this already available?).
However, another solution that should also be in place is an "Unassigned" subcategory to take the place of the category being the "catch all" of elements not subcategorized. This would mean that all items would by default technically have a subcategory, but some would just be (worst-case) left as "Unassigned", but still allowing for the rest of the families and elements to properly be controlled by subcategories.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.