Component Folders

[Louishitchcock]

I've been working on a project for a couple of days now and my assembly is getting bigger and bigger - with this an increasing amount of hardware is building up on the component list - I have over 200 bolts and it is becoming tricky to manage what components are actually needed - so I propose a way to create a folder in the component list on the left - much like what happens when you create a view I think that you should be able to create a folder of components, this will also allow the user to quickly turn off unnecessary components such as nuts and bolts; this also allows the users with lower-end computers to better scrub through there design without major optimisation. The user should be able to just 'Drag and Drop' the components into and out of the folder.

[HughesTooling]

You can use a component as a container for sub components but you need to plan ahead, although you could drag components into a component now and create a sub assembly it would make mess of your timeline.

If you'd created components to contain your fasteners first then with them enabled inserted your linked files it could look like this with a neat organised timeline and browser. Have you found the Rule#1 thread?

Mark

[Anonymous]

Yes I manage hardware by making a "New Component", renaming it so something obvious like "Hardware", and dragging the hardware components under it.   It's easy enough to do that way and acts like a folder.

[Anonymous]

When you turn off 'capture design history' it enables the ability to organize the browser folders exactly as you want. You can copy and paste components, bodies, and so forth in any directory level that you choose. When capture design history is turned on the browser does not let your modify the positions and levels of the browser files. Working without design history being captured is great for increased performance and smooth quick functions of the program however, you miss out on a few key features such as being able to select items on the timeline when creating patterns and things like this. Also, without design history you lose the ability to back track on your work when you discover an mistake or error in your design work. I usually don't use design history but that is because my computer slows down with design history being captured because sometimes an action is performed that requires the computer to process all the integrity and order of the timeline which can sometimes be a real hassle for waiting time.

[Anonymous]

Ahh yes another Fusion 360 issue. I typically do not use Design History for the same issues that you have stated. Large, complex assemblies do not do well with it and yes of course you lose parametric behavior when you turn off the design history. I believe that you can toggle the design history back to on after you have moved the folders, is this correct?

[Anonymous]

I do believe so. When turning 'captures design history' back on Fusion 360
just creates a special file in the timeline that is like a filing cabinet
of history actions or more like a summary of history events and then it
starts up a new action recording timeline from that cabinet file position
in the timeline and then it adapts to the existing organization of the
browser files.