Layer Reorganization Improvement
It's 2022, and the Layers need to be draggable to ANYWHERE except into a root or of itself (or any crazy circular ref conditions)
I have some kind of ADD or OCD that makes it exceedingly demoralizing and frustrating that, when I get too far into a layer org, I can't drag things where I need them. If I start off with a SWBS structure, but need to modify it along the lines of a cross tab, I usually end up tossing a file that may have hundreds of layers.
Or, in fury, I plod on, knowing that whomever I give or sell the file to will have a lot of questions about my rationality or sanity. I suspect Shark is powered by a database of some kind inside, so, my simple brain ponders why that power is wasted or gatekept.
If Shark were to swim into 2022, and remove the articifial or cruel patent obstruction, or whatever it is hamstringing/hobbling Shark and Shark users, life would be hugely improved for me.
FURTHER....
Further, it would be nice if the user can create a spreadsheet mapper by exporting the layers to a BOM-like text file, bringing it into preferred spreadsheet app (please, please, do not impose a specific company, just keep it simple text, importable and exportable), editing it, and telling Shark to tell its database to remap things.
I'm not a programmer, but, given how powerful Shark is, I can't believe such would not be possible without breaking Shark. Just import and export the unique geometry values, and, on import, check against unexpected or inadvertent duplications. Shark could if necessary keep hidden a proprietary internal mapper. I could care less, as long as I can be free to import/export text and not be forced to use any spreadsheet app not on my system. Text is a nice, simple, fair, universal, friendly default.
ZeroLengthCurve