Automatically create new component when starting a new file

[alexhardie]

Hi, I asked about doing this in another forum and I was told to come here.  I often forget to start a new component when starting a new design.  This means that any other component I create is a sub component of the original.  Is there a way to make it so a new component is automatically created when a new design file is started?

Thanks,

-Alex

[goyals]

Hi Alex,

When a new design is started, there is already a component which is root component of the design and named as "Unsaved" by default. When document is saved, this root component is renamed as the name of document. Is it not what you intended?

Regards,

Shyam Goyal

[alexhardie]

I would like to by default have a sub component created.  In the case that I later want to turn my part into a assembly of parts, it works better if each subsequent part is not a sub component of the original part, but rather all the components are sub components of the top level component.  Somewhere there's a tutorial on fusion 360 that says you should always create a new component right away so you don't run into this issue.  For instance, if I create truck wheel, then later i decide to create the truck, the truck would be a sub component of the wheel unless I remembered to create a new component first.  I could always create a component from a body, but then it doesn't work as well with the design history.  I think every new part file should be assume that it will someday be an assembly.  Let me know if I'm missing something.

[goyals]

May be I can pass this to concern team so they can evaluate this requirement. One idea might be just to add a preference setting which is default to the current behaviour and if a particular user always want to start a new design with Sub-component then it is allowed by setting it in preferences.

[Igorva]

interesting idea!

[alexhardie]

Another idea could be to allow the designer to bump the top level "parent" component down one level so "sibling" components can be created.  Or allow sibling components at the top level.  I think this idea has come up in the past, so maybe there's a good reason it hasn't been implemented.