I have several documents with multiple layers, and by multiple I mean up to 100 or so. They are all very simple layers, most times with one word. The files are for printing to a laser engraver which has a standard shape on one layer, and the rest of the layers are single words that are centered to the shape layer. When I print, the shape layer is "visible" but not printable or selectable. Just one text layer is visible, printable, and selectable (for the purposes of printing "center/center" to the center of the wood piece being engraved). So, I'm only printing one layer at a time.
Here's the issue: The object manager obviously has a multitude of layers, all of them invisible except for the layer to be actually printed, and the shape layer visible just for visual reference. Many times, when I change a layer to invisible from visible (or vice versa), or change a layer from printable to non-printable (or vice versa), or make a layer selectable to non-selectable (or vice versa), the object manager will jump to another layer entirely, marking that layer with the change I made to the original layer (while also making the desired change to the original layer). So, it's doing its job, and then some. If I change layer 27 to "visible", for example, object manager will also jump to layer 54 and make the same change. I have to change layer 54 back to "invisible" and scroll back to layer 27 to resume work. I'm lucky, I guess, that at least it goes right to the unintended layer when it does this jumping around, but I still have to find my original layer to resume work. It happens with every change, so I'm spending a lot of time jumping all over the layer list in object manager. I can't seem to come up with a pattern for this behaviour, it seems the layers with the unintended changes are randomly chosen.
Sorry about the length of this question, but it's a little difficult to explain. I guess this might open up the discussion of "how many layers is too many layers", but these layers have extremely limited simple content.
It seems that the behavior is present at the opening of the file, I don't seem to remember it "cropping up" after some previous operations that succeeded. These are all page layers.
I reread my earlier post, and I don't want to give the impression that the weirdness starts midway through working on a file, it seems to be there or not from the start. I can tell you that any file created to run this epilog engraver will tend to have many layers, sometimes numbering a hundred or so, but each layer has very simple content (like, as you say, one word of artistic text), and only one layer at a time is printing.
That is a great macro. I'm not sure that it would be of help in dealing with the jumping around between random layers when settings are changed, but it opens up a lot of other ideas for me as to how I arrange my layers. Excellent.
It depends on what is causing the "jumping around". If the Object Manager is incorrectly applying the changes you are requesting, then you might be fine with the macro, because it is "flipping the switches" for the layers.
If you are interested in trying the macro, then contact me by private message through the forum, and I'll get you something to try.
It would be hard to claim that the object manager is incorrectly applying changes, it's just that it is applying the changes additionally to another layer unrelated to the original. It's overachieving. Unfortunately, it leaves me in an unintended place on the layers list, with some repairing and navigation ahead.
You wrote that clearly in your opening post, and I failed to pick up on it.
The good news is that I think I've found a way to replicate the bad behavior!
If I have a single object selected, and the layer is expanded in the Object Manager, then the Object Manager wants to automatically scroll to get the selected object into view in the docker. If the Object Manager is set to "Expand to Show Selection", then that will happen automatically any time an object is selected.
It seems that, when changing visible/printable/editable for a layer, the Object manager makes the change, then scrolls to bring the selected object into view in the docker - and THEN toggles the same setting for whatever layer happens to be under the mouse pointer!
If I try to perform similar operations without having an object selected, then the Object Manager does not keep automatically scrolling; no problem.
Here are two videos. One of them has an object selected; the other does not.
VIDEO: Object Manager over achieving
VIDEO: Object Manager just achieving
You might have to download those videos and play them locally. Google Drive seems to be slower than usual at processing them to allow them to be viewed in a browser.