Thanks again.
SOLUTION
Not easy to fix since a library usually contains only parts of the category tree, not all of them. Let’s consider a category “A” is in library “L1”, and its child “B” is in library “L2”. If L2 is not installed and you open L1 in the library editor, the parent category of B is not available so it’s impossible to render it correctly.
Maybe for such cases a virtual “Unknown” category could be displayed instead, probably we need to make some experiments to see what works well.
This may be wrong but it strikes me that when placing a component you get the TreeView and then when you are building a library you can bend it to kind of do the same.
What I find is that if I scrub the lot and load the recommended libraries they seem to be fragmented in terms of Symbols/Components and Packages/Devices appearing in different places/libraries but they are referenced back up the tree using dependencies. A library can depend on another library.
This might be what you are referring to in terms of dependencies. Perhaps a Device in one library refers back to a Component in another, further up the tree, library. I’m not so sure it should work like that but I’m not trying to make waves. As it stands it can be kind of bent to my way of thinking.
I don’t hit Symbols/Components and/or Packages/Devices until I am at the bottom level of the, it is what it is, tree of libraries. I have not fully tried it but I was wondering if I could load the recommended libraries and reference a dependency back from one which I had created back into one of them but that does not seem to work.
Unless I have missed something, I probably have, it seems that it should be possible to collapse everything back into one tree from the outset without breaking things. However I’m not the person doing the programming and since I can bend it to make it work the way I would like I guess it’s not a problem.
I’ll just suggest that at first glance, for the average idiot like me who does not read the manual… I missed the dependency thing, it could make more sense and overall give a tidier and more meaningful result at that first glance and later on. Rather than having multiple open library windows it could be folded back into one with the Symbols/Components and Packages/Devices only being displayed when the main Tree is expanded to select them.
Apologies if that does not make sense.
Ooops. Having babble on I appear to have lost the dependencies. They were there and it still seems to work without them. Grrrr. I’ll go put them back in. No… it throws them away again. I guess since there is no referencing back to an actual ‘thing’ I’m still doing it wrong. No. I had broken something else by renaming something.