Is there a way to move a layer (and all sublayers) to a new layer? I'm not talking about moving the layer on the display list... I'm talking about moving the entire structure of a layer to a new layer.

Say I have:

Layer1
-Layer1sub1
-Layer1sub2

Layer2

Can I move Layer1 (and all subs) to be a sublayer on Layer2?

Intuitively, this would be a click-and-drag kind of event, but that doesn't seem to work.

Thanks!

Jeff

Click and drag of layers does work, but it uses the VERY unintuitive Shift key.

Like Jean-Francois wrote, you can not drag or move layers between groups or levels, but if you use the layer mask to select everything on the layer you want to move, and paste into the new layer. Its a kludgy work around, but better than nothing.

Thanks all. I guess there isn't an easy way to move ~75 layers... I did it "manually" as suggested and it worked out. Has a "click-and-drag" layer management feature been requested in the past? If not, would that be useful to everyone?

Click and drag has been requested many many times. Shark V7 gave us Shift+Click+Drag but as stated it is limited to moving layers within a group at the same hierarchy.

True drag and drop layer management is a dream that has been requested more times than I could count. Sadly interface enhancement like this appear to be very low on the list.

I JUST, serendipitously, inadvertently figured out the Shift-Click-Drag.

I do not know WHY in the past every attempt failed and drove me mad.

So, to spare others of agony:

-- Click ONCE on the layer you want to move (do not double click into the layer's name)

-- Press and HOLD shift

-- Start Dragging the layer you want moved

-- RELEASE the shift key WHILE dragging is in motion

The layer name should float translucently as the mouse is moving the layer in the view.


This is soooo cumbersome and fraught with haphazard and stressful repeate attempts. It should be possible to just quick-click and drag. My blood pressure actually goes up markedly when trying to make something work. I bet even monks and Sifus would struggle to hide their frustration.

But, now that I got it to work, if FEELS better than right-clicks action.

All this content is justt streams of code in some array-based table/database in the file. It is mindboggling that content cannot be moved betwen trees.

It needs to be retroactively patched.

It also should be possible to multi-select layers to be dragged/slid/wedge-inserted in between any layers in the view, not just a given level. As a user of and dabbler in databases and tables, this baffles me.

I REALLY like Shark, but little itty bitty areas of partial polishing just make me look stupid when would-be users get to that point. *I* can put up with it because I like most of the GUI, and VC/VCP/Shark are a helluva lot closer to how my mind moves around in the view than my 2 months in rage in stress with another couple of CAD apps I dumped before switching to VC.

I cannot credibly compel admirers of my drawings to use Shark unless some of these quirky little things get addressed. Some users want new features, and some want the whacky things hammered down first. I'm in between.

Please, retroactively patch the layer tree management.

I thought there was a post about enhanced filtering, such as finding things by name, color, parftial name, attributes, and so on.

Please, also make it possible to MIRROR objects and have their counterparts remain on the layer of their parent.

Also, please make it possible for the user to set up mirroring rules. For example, if working on port and starboard geometry, and I mirrror starboard objects which are on intuitively-named layers, it would be nice if Shark would clone the layer (or offer to do so) and smartly drop the mirrored stuff on the corresponding layer. This would go miles toward alleviating the user of crafting special filters just to remove stuff from view.

Freeship/Hydronship (FS/HS 3.4x) can do that partially. When mirroring a piece of geometry of the ship, it asks whether or not the mirrored items should be linked or not linked to the parent. When the mirroring operation is complete, the original stuff is still in SELECT, providing the user an ability to simply and quickly delete that material without having to re-select it. Also, all the attributes of the original material (specific weight, thickness, and colors) travel with the mirrored stuff and stay with it even if the originals of the mirror are deleted.

Just some of my feelings/thoughts/ideas/observations.