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

    This should be a simple enough feature to create. The “default” state should always be the “Master” state, one that controls the content of that instance, then a Name editable first state would be created.

    This would still allow a master component to control and change things, via the master state and likewise, changes made to individual states would “unlink” from the master state as it goes now but it would give control to things like text, color, size and even placement on our instances of a component in files.

    It’s imperative to add this functionality as using it in the current state completely invalidates creating library components that have any complexity.

    Brandon supported this idea  · 
    An error occurred while saving the comment
    Brandon commented  · 

    There are moments where you'd want the instance to have different states that aren't copied. For example if you are trying to do a specific override.

    I think this requires a little thought, which is why it's still under review. Maybe if "default" were template instead and you are required to create all states from there.

    I already do that in some cases already where I'll leave the default as the true master then create a new default state so if I have to go back and make a change to only the default, it doesn't make that change on all of my other states that I then have to go through and make changes to all the other states to undo it.

    That being said. I'd love to be able to make text and size changes on a copied component in that "Default/Template" state and make it transfer to the other states in this instance.