Scale as a property

This would be SO useful. Especially for prototyping any zoom/scale UI.

Warning: noob comments below 🙂

Yes. This.
Scaling seems to occur from the TL corner by default.
As a noob, I may be misusing the term, but I am truing to make a variant that has been enlarged using the handles… and animating between (effectively a scale), and no matter what I try, the animation is anchored to the TL of the default variant.

I hope there is a way… (sort of an “action center”???)

What needs to be rethought is the entire notion of properties.

They should not exist (this will confuse so many people)…

Everything should be a behavior. There are monumentally good reasons for this.

You just need to add a hug content to each individual icon size and that will prevent the icon from being resized through the master component.

Hey Ben! i’m struggling with exactly the same issue - Read through all these comments here but doesnt seem like it got fixed…did you figure it out somewhere else?

Did anyone figure out a fix for this? Here is a screenshot from the master icon library file i’m using where you can see the layers. If I should adapt the master icons, please let me know what I should do.

replying so this doesn’t close

+1, I have icons at 24px with an intent to scale uniformly, but where I’ve used stroke inside boolean operations (to preserve editability), these aren’t scaling while in a swapped and nested instance.

Hopefully it’s clear in these images; the icon is scaled to 32px using the scale tool, but when swapped, the stroke weights are not scaled.

Yes, I need this (or similar) or I’ll be unnecessarily duplicating (or flattening) an icon library for the sake of strokes that don’t scale.

I use booleans to preserve underlying strokes but these don’t scale when in swapped and nested instances.

This is a serious issue that seems to be re-introduced with recent updates. I believe there is something happening when there are nested variants inside of a new master component. See video: