Separators in the browser

[kacper.suchomski]

Sometimes I make very complex models with a long design history. This makes scrolling through the story very tedious.

Some time ago I asked for the ability to dock key browser elements (see the comment with the video under this post):

https://forums.autodesk.com/t5/inventor-ideas/docking-the-main-parts-of-the-browser/idi-p/11683473

This time I want to suggest the possibility of adding separators in the model history. Such a separator would have two functions:

1. Separation of individual modeling phases. Typically, entire sets of commands apply to a specific modeling stage (or solid). This would make it easier to find the right operations when you need to edit.
2. Minimizing a set of operations. Such a separator should allow the operations contained under it to be collapsed (hidden).

[bradeneuropeArthur]

You could also use the derive methods to separate things from each other.

Maybe it will also be a good idea to add folder structures like they are available within the Assembly Document.

[kacper.suchomski]

@bradeneuropeArthur  yes, it makes data management easier downstream, but not in the concept modeling phase. Sometimes I have to make really "long" models that require changes on the fly.

[bradeneuropeArthur]

Absolutely true that it makes things not easier when derive is used, solving a problem.

I like to keep things simple and out of the box as much as possible without using to much of levels and references.

But that is more of a different topic, isn't it?

I am sure that many votes will follow....

[pate_mackenna]

I had this idea swirling around in my head for a while.  I also use a part modeling technique that results in extensive feature trees.  It's good to see interest in a focused solution that may also be achievable, compared to the feature "folders" idea.  That one seems to be going nowhere.  Kudos to @kacper.suchomski!

For context, this type of collapsible grouping can be seen in tons of popular software interfaces.  Its usefulness is hard to deny.  Here are some examples:

in iLogic        😉

  

in Excel

...@dan_szymanski?

[dan_szymanski]

@kacper.suchomski & @pate_mackenna, thank you for outlining the challenges and the problem you would like solved. The video provided displays a very complex browser tree. I will pass this along to the team @jason_hetu & @SteveMDennis ). Browser folders, browser separators/sections, frozen headers, browser splits - all great ideas to review and consider when attempting to solve the challenge of a bloated browser tree. Thank you!

[kacper.suchomski]

Thank you @dan_szymanski 

I mentioned separators instead of folders (which we can use in assembly), because I think that separators (with a small "+" icon to shorten / expand content) do not affect the tree structure, which would be disadvantageous. Folders create a kind of hierarchy, and here it is about compactness of the list of operations, but without affecting the quality of the model history.