Convert component to sub-component

[gman-r]

While it is nice to be able to model multiple components in on environment, I can't count the number of times I start designing something and then realize that it should have been in its own component  because I will need to add other sibling components. This happens very often that the top level when a new document is created. You immediately start modeling your idea only to realize that you need a peer sub component.  It happens so often and can be so painful to unwind, I almost prefer being forced to model component by component like it worked in solid works. It would be very useful if you could just move the contents of the component into a new sub-component. That is, contents of the component would be moved down one level into a new sub-component under the original component. Then I can create the peer sub component. This is especially useful for the root component since you cannot create a pear to the root component.  Eg:

[mike]

You can already do this. I have been doing this for bolt groups, and things like air cylinders.

Insert bolt from mcmaster, this creates a component. under what ever component is active. If you do this at the top level, it will be its own component.

Create another new component from the top level, rename it. Now drag the sub component onto the header/title of the new component. This will make it a sub component.

[gman-r]

Hi Mike, 

Thanks for the reply, but the feature I asking for is a different from what you are describing. In your example, you started out with components in the first place and you just want to move them around in the hierarchy. But imagine if you started a new file, drew a few sketches, created some features, and then realize that some aspect you were about to model needs to be its own component. If you were forward looking enough to have created a sub component under the root and did all your work there, then you are fine, you can just start a new component under the root. But if you did all the aforementioned work under the root component for example, any new component you add will now be a mix of the features you already create and any components you add. Effectively any component you add from this point on will be children of part you started modeling at the root even if they were supposed to be peers. To the best of my knowledge, the only option you have to correct it is to:

1) Save the file, create a new file, insert the saved file as a new component in the new file, add the peer components as independent components in the new file(and hope you don't make the mistake again while modeling one of the new su-components). 
2) Create a new component and manually redo everything you did(copying when possible but generally does not work well) in the new component and then delete all of the features and sketches from the root component. 
3) Completely start over and think ahead to create the right components from the start.

What I'm asking for is to have a way to at any time, nest the whole contents of a component in a new sub-component. So If i started designing something and then realize it really needs to be done as multiple component, I can just move the current work into a sub-component, and then add any other peer components that I need.

[TrippyLighting]

@gman-r present a particular case on the general forum and I can show you what can be done, what can't be done and why. Some of this is possible.