This is why I have the 'sorted' section in the default part bin of my LDCad. It supplies a somewhat friendlier (sub)category based tree. For example I've split bricks into: plain, bricks with stickers, slope 33deg, slope 45def, etc etc
Do note these are just the default bin groups (sorted section), users can add unlimited custom ones or create entire custom bin trees independent of categories etc (using filters or even handpicked part lists).
Recently I wanted to create an upgraded (more user friendly) sorted tree but I'm not familiar enough with all the parts to create a more efficient tree.
Might be bit off topic, but what I'm trying to say is these categories etc are there to be used as a base not 'one on one' imho, the Library is getting to big for that.
Do note these are just the default bin groups (sorted section), users can add unlimited custom ones or create entire custom bin trees independent of categories etc (using filters or even handpicked part lists).
Recently I wanted to create an upgraded (more user friendly) sorted tree but I'm not familiar enough with all the parts to create a more efficient tree.
Might be bit off topic, but what I'm trying to say is these categories etc are there to be used as a base not 'one on one' imho, the Library is getting to big for that.