Feature Request: Parameters dialog improvements

Feature Request: Parameters dialog improvements

MaffooClock
Explorer Explorer
159 Views
1 Reply
Message 1 of 2

Feature Request: Parameters dialog improvements

MaffooClock
Explorer
Explorer

I've been using Fusion for about four years, and one element that bugs me the most, consistently, is the Parameters dialog.  Fusion has a ton of advanced functionality, but the Parameters dialog looks and functions as if it hasn't been touched in decades.

 

1. Sorted column should be remembered

I usually prefer alphabetical order by Name, as my parameter names often include grouping connotations.  Why can't this be memorized so I don't have to click the Name header every time?  Seems like an elementary function that every UI designer implements as a matter of common practice, so I'm a bit surprised that it doesn't already exist.

 

2. Dialog size and column widths

I see that the dialog size and the column widths are remembered, but only for the current session; upon closing Fusion, then later opening the Parameters dialog on subsequent runs of Fusion return these to default sizes.  This memory should persist per-project or globally, not per-session.

 

3. Get rid of the "User Parameter" column

There is already a section heading labeled "fx User Parameters", so why does "User Parameter" also need to be displayed in every row?  Seems like clutter and an unnecessary waste of space.  Just have the value from the Name column appear in this first column instead (then you won't need a Name column).

 

4. Parameter groups

As mentioned in #1 above, I tend to name my parameters such that they group easily when sorted by Name, e.g. ComponentName_FeatureName_Attribute.  While this works well enough (especially if the dialog would remember my preference to sort by Name), it would be even more useful to be able to create groups that could be folded and expanded.  Notation would then be something like GroupName.SubGroupName.ParameterName, or as in my example, ComponentName.FeatureName.Attribute -- consistent with current parameter naming, just with period characters between parent group names.

 

 

That last one is really just a nice-to-have feature, but the first three (or first two, at least) should be no-brainers that I expect are easy to implement.

160 Views
1 Reply
Reply (1)
Message 2 of 2

Romain_is_me
Explorer
Explorer

I agree with all; it does seem like easy to implement UI stuff. Other things I've noticed:

 

5. Size of dimension typing box. If you're setting a dimension to some combination of variables/functions, the box doesn't normally expand.

This means that you have to hold the arrow keys down to scroll to read small sections at a time to check, make edits, or copy a section.

 

It's occurred to me that the proper practice might be to use an additional function, which references the relevant functions, and use that. 

 

However, similar to the column width issues mentioned, even in the parameters dialogue it can be quite tricky to have a large functions, and sloppy to need to use layers of sub functions.

 

6. As far as I can tell, you have to close the parameters dialogue to do anything, which interrupts workflow (constantly exiting then hovering over modify and clicking on parameters; why have that button hidden in a drop-down?).

 

7. Organising files and folders: what's with the "move" in a drop down instead of drag and drop? There's got to be a reason why it doesn't use the standard system of every other file/folder UI (drag and drop).

Maybe its considered too easy to make mistakes with drag and drop and end up confusing organisation? I don't know, it feels pretty clunky though.

0 Likes