Skip to content

Settings and activity

2 results found

  1. 69 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
    Wolfgang Harland commented  · 

    So currently, you can use "Reset to Main State" in order to relink all properties back to the main component. It would be great if you could open some sort of checkbox menu that allowed you to relink or unlink all the various property relationships.

    This would be helpful when designing for various breakpoints. Maybe my main component is on my smallest breakpoint. Then, I build out my next (medium) breakpoint and I make some changes to this instance (call it instance #2). Then I copy that modified instance #2 to make instance #3. I like most of the modifications that I had made to instance #2, but I realize there are certain properties that I actually want to relink to the main component. Let's say that, in instance #2, I had changed a whole bunch of things, including the stroke weight of an ellipse and it's position. I decide I like that modified position, but I want to relink the stroke weight. I could navigate to that ellipse, right click, select "relink properties" and a menu of checkboxes would pop up. All of the various linked properties would be listed, but I would see that "X,Y Position" and "Stroke Weight" were unchecked. So, I could just check the box for stroke weight, and viola, the ellipse stays in the same position, but the stroke weight is now tied back to the main component.

    Wolfgang Harland supported this idea  · 
  2. 56 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
    Wolfgang Harland commented  · 

    Let's say you create component A. Then I duplicate it to create instance A'. Then I break some some links (I don't know, maybe I change the color and reposition some things). Then, I duplicate A' to create A''. Currently, both A' and A'' will still follow modifications to A, as long as those feature links haven't been broken. However, if I further modify A', this will not cascade down to A''. I want a system where modifications to A cascade down the chain to A' and A'', and modifications to A' will cascade down to A''. Essentially, instead of each component instance only having a single parent, there is an actual lineage of components. A is essentially the grandparent of A'', and A' is the parent of A'.

    This would be incredibly helpful when doing responsive design for screens of various breakpoints. As I design each new breakpoint, I could make modifications to the components within it. Then, when I move onto the next breakpoint, new relationships between each iteration can be maintained, while also keeping everything consistent with the component instance that preceded it.

    Wolfgang Harland supported this idea  ·