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
    cmmartti commented  · 

    One ugly work-around to this is to use a sub-component that holds all of the state modifications. So if you have a Button master component, add the template text, then nest a Button_State component instance inside it that holds everything else (background, shadow, etc.). The Button component doesn't have any states, but the Button_State component does.

    Then for every Button component instance, you can modify the text at will, then click through into the nested Button_State component and change the state. One limitation to this workaround is that you can't modify the text properties (colour, size, etc.) because it's not located inside Button_State. Also, you'll have twice as many components so best to use a consistent naming scheme.

    cmmartti supported this idea  ·