Obviously the part workspace is history based, and the order in which features are built have affect the outcome, hence the dogbone and all of that.
But why can't we re-order the items in an assembly workspace? GM already sorts parts to the top of the list and subassemblies to the bottom, so it must be possible to some degree. Other than this, GM simply adds new items in the order they were added to the assembly. Same with constraints.
I find myself wishing I could change the order of parts/assemblies and constraints, just for neatness and ease of finding parts in the assembly Explorer. Hardware, for example, is a big one. When I build assemblies I often find that hardware is randomly scattered along the list; sometimes I have to change or add something at a later time, and that part is going to be way down the list from the others it should be with. Likewise with assembly constraints. If I have a certain mate pattern for a repeating subassembly (that can't be handled with the assembly pattern tool), it would be useful to have those constraints living right next to each other on the list.
In the grand scheme of things I'm sure this isn't that important. Just something I wish I could do to smooth out the workflow a bit.
But why can't we re-order the items in an assembly workspace? GM already sorts parts to the top of the list and subassemblies to the bottom, so it must be possible to some degree. Other than this, GM simply adds new items in the order they were added to the assembly. Same with constraints.
I find myself wishing I could change the order of parts/assemblies and constraints, just for neatness and ease of finding parts in the assembly Explorer. Hardware, for example, is a big one. When I build assemblies I often find that hardware is randomly scattered along the list; sometimes I have to change or add something at a later time, and that part is going to be way down the list from the others it should be with. Likewise with assembly constraints. If I have a certain mate pattern for a repeating subassembly (that can't be handled with the assembly pattern tool), it would be useful to have those constraints living right next to each other on the list.
In the grand scheme of things I'm sure this isn't that important. Just something I wish I could do to smooth out the workflow a bit.