Re-Order Parameters

[Lonnie.Cady]

Is there any method to change the order of parameters?

I have many that I want to fill in to control geometry.  I forgot one and now it falls at the end of the list.  It would make more sense in my workflow it was in sequence with the others for that piece of geometry.

[pbateman27]

Agree 100%

[Scoox]

You know what would be really useful? If parameters could be defined with component scope, this way, names could be reused but only used within the scope of their respective parent components. That, or the ability to create a folder structure in the Parameters list, so that parameters that belong together conceptually can be grouped some how.

[wesc779WC]

Just chiming in that being able to reorder parameters is one of the first few missing features I check every time a new F360 lands.   Always disappointed.    it really seems the devs prioritize fun features vs basic QoL features.   (Mac stability is least priority, btw)

[david_maiden]

For those who are going to dig up this thread, if you really need to order parameter there is a hacky way to do it.
Since you can sort parameter by name, you can just start all you parameters by an index (1_TopHeight, 2_TopWidth, ...)
Be warn, this is a very clumsy solution.

[overmars_jelle]

Still a hacky way, but works pretty fine. Hierarchy in the parameter list would be the ideal solution.

Meanwhile... In a fusion environment, where a list of parameters spans multiple components, having a naming convention that incorporates the name of the highest component where each parameter is used can significantly enhance both clarity and usability. This concept works much like breadcrumbs on a website, providing a clear path back to the primary context of each parameter.

For example, consider a cabinet with multiple components, like a *Foundation* and *Cabinet Dishwasher*. By naming parameters such as `FoundationHeight` or `CabinetDishwasherHeight`, you can immediately identify the origin or main usage area of each parameter.

When these parameters are sorted alphabetically, this structure allows users to effortlessly group and locate related parameters. For instance, all parameters under *Foundation* would appear together when sorted by name, giving a quick and intuitive overview of every configurable aspect related to user authentication.

This saves time, allows you to add parameters at a later point, avoids confusion, and minimizes the risk of errors when managing or adjusting the system's configuration.

[Scoox]

Yeah that's the way we all do it, or similar. I name my params systematically. For instance: Bushing_Length, Bushing_Diameter, Bushing_FilletRadius, etc. This way after sorting all related parameters appear grouped. The number prefix trick works but is impractical because often you need to add a parameter between two existing numbers which breaks the sequence (that or you end up with repeated numbers or "1.2" numbering).

The real problem is that the parameters window does not remember the last used sort. This means users need remember to sort the list manually every time the Parameters window... in the age of AI, that is. This is so ridiculous it's beyond belief.  The devs already did the difficult part, which was overhauling the Parameters window and making it sortable. Next to that adding a little checkbox there that keeps the last sort is a walk in the park, in fact, it'd be cool if whoever designed this would chime in and tell us all exactly under what circumstances chronological sort would be beneficial. Personally, if there was a global setting to permanently use ascending alphanumerical sort by name, that would be my preference.