Skip to content

Settings and activity

1 result found

  1. 1,472 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Martin commented  · 

    I wholeheartedly support this request. It's not even a feature request but feels more like a bug. For me the current behaviour is really frustrating and I often find myself using separate components for what should have been states. For example, I can't have one button with disabled, pressed at whatnot states (that only differ by colour) simply because when I place an instance on the comp I have to go and change its label throughout all states and if the label doesn't fit I have to change the instance's width on all states, etc.

    For me the best way for this to work is to treat custom states somewhat like instances of the default state – if a parameter is not overriden on the custom state, propagate it's value from the default.

    Martin supported this idea  ·