Improve New Variable UX

Lazlo Bonin (Lead Developer) 5 years ago updated 2 years ago 11 1 duplicate

The new variable UX is confusing. Users often forget to fill a name before hitting the plus button. Redesign and implement a better workflow.

Bolt Version:
Unity Version:
Scripting Backend:
.NET Version (API Compatibility Level):

Duplicates 1


A option to create a new variable inside the flow graph and select existing variables would be great.

Create Var

Select Var

yes, I second Elin's idea


Noting from Marshall's merged post, put the new variable field at the top of the collection to avoid having to scroll down.

This is a small UX improvement, I think, if we delete a variable that is currently being used there should be a warning prompt. I mean we don't even need to check if the variable is being used or not just always warn the user would be a good thing since it's potentially a destructive action. I happen to delete my variable a few time by mistake that's why I'm bringing this up.

I have another UI Improvement I'd like to mention, it would be a nice-to-have if we can drag on the variable name to modify the value if they are int, float, v3, etc.


You can do that by holding Shift over the field!

nice! but un intuitive(

I know :( But unfortunately it would be extremely hard to refactor the inspector code to do it on the label field. Also, if it only worked on the label field, then you couldn't do it from within a unit in a flow graph. Or change a single field from a vector input, which you can to with the Shift technique!

this changes everything O.O


(Sorry for the bump/necro, I'm doing some roadmap grooming following the Unity acquisition!)

Marking this as completed with Bolt 2's entirely reworked class variable system. The workflow has been improved significantly!