[Feature Request] - Define steps in interactable progress bars

[zRevenger]

Hello,
I would like to request if possible to optionally add steps in interactable progress bars, to ensure easier and more rounded value definition even for floats.

Example of implementation:
[ProgressBar("Example", minValue: .5f, maxValue: 3f, IsInteractable = true, step: .25f)]

Currently, when using floats, you would get values that go down to multiple decimal places. For example reaching an exact 1.5 would be hard, but i'd most likely get something along the lines 1.505693

[zRevenger]

I have looked into this and it is definitely doable by adding a property in the ProgressBarAttribute

public float Step { get; set; }

And then editing the ProgressBarAttributeDrawer

        private void SetProgressValue(SerializedProperty property, Rect progressBarRect, float xPosition)
        {
            var minValue = Attribute.MinValue;
            var maxValue = Attribute.MaxValue;
            var step = Attribute.Step; //Here i added the step

            var range = progressBarRect.xMax - progressBarRect.xMin;
            xPosition = Mathf.Clamp(xPosition - progressBarRect.xMin, 0, range);

            var fill = Mathf.Clamp01(xPosition / range);
            var newValue = (maxValue - minValue) * fill + minValue;
            //If the step has a value that is not 0, it will calculate in the step
            if (step != 0f)
            {
                newValue = Mathf.Round((newValue - minValue) / step) * step + minValue; //Calculates the new value with the step
                newValue = Mathf.Clamp(newValue, minValue, maxValue); //Then clamps it just to be sure
            }
            
            switch (property.propertyType)
            {
                case SerializedPropertyType.Integer:
                    property.intValue = Mathf.RoundToInt(newValue);
                    break;
                case SerializedPropertyType.Float:
                    property.floatValue = newValue;
                    break;
            }
        }

Can this be done better? most likely, but it can be implemented for everyone to use if you want. (Tested and working)

[arimger]

Hi! Sure, I will add it in the next update!