Is it me, or is it not just me?

VCP (IIRC) and definitely Shark LT won't keep open all the drawings' branches. The branches of the second and subsequent drawings persistently collapse either when I leave them or when I return to them.

I open a drawing. It's layers may be opened/expanded as last saved. I go to a second drawing, I have to expand branches to get to something. I return to the first drawing to edit, then need to return to the second drawing.

When I get to the second drawing, the brancheds are collapsed. The NEVER, NEVER, EVER, stay as I last left them.

Working with moving content around is becoming excruciatingly maddening. Every time the non-first drawings are returned to, I have to re-expand the branches. Thist just SAPS my will, ruins my concentration, and just exaspirates me. It just kills my will to want to continue working.

Can there be a patch for SLT v8 SP 1 that tells Shark: "NEVER 'knock off/undo' the user's branch expansions without explicit user input. EVER!", or something like that?

It's just I'm getting to the edge here. I can't transplant, zip, snip, move branches or layers around between my OWN DRAWINGS! I cannot export them or import them and expand them with their content. I can't copy geometry and paste into a parent branch and have the program bring in the layer or branch/tree name with the geometry.

When I work on files, I should do SOME planning. But, I do not have a crystal ball. When I need to fork a file to do a side study/scenario with some curves, then spend a couple days evolving the thing, it becomes demoralizing to contemplate ALL the work that has to be done with layers JUST to incorporate those changes into the original parent drawing.

Tim & Team, please, please show some mercy and once and for all make it possible via new releases AND patches to at least one rev back (VCP 7, SLT 8/Shark8) and fix these two problems that are just killing me.

To be hones, layer issues are one of my hugest banes. These layers and branches all must have some internal audit/serial number. As long as geometry being moved around is not from foreign apps, it should import. If it has a collision risk, just internally disallow interaction between the incompatibilities. Force them to show a flag on the layer name, but let the user have the geometry show up.