Scale as a property

@Gavin Yes, exactly. I honestly don’t think it would complicate things, but I’m sure there would be a few wrinkles to think about. I was envisioning a literal scale input that would scale everything inside the frame (stroke, corners, text, etc…), exactly how it would work in development. Although they are not a design tools, Principle and Origami have this for prototyping and it works well.

As I’ve said before, the current scale tool isn’t really a true scale tool. It just uses a scale to calculate computed dimensions; which you’ve mentioned is destructive and frustrating to control.

Interestingly there is already a concept of a scale property underneath the hood, (see Figma Plugin API) but this only exists on instances I believe.

Guess I´m struggeling with the same issue.

There are so many plugins called scale, skale oder scale whatever, can you let us know which one it is? <3

This one!

So you can scale at least something in height or width or in percent. but it does not what I want. The idea is that after changing an asset the list entry gets the height of the new entry. actual the old entry pretends the height. so if I switch an entry it the list entry should change to the height the new entry actually has. And I dont want to change it manually as I have a huge bunch of lists where this should happen … but thanks anyways <3

yeah this is not something that a plug-in can solve I’m afraid. I noticed that this issue happens only with nested components, so if you find a way to avoid nesting comps the scaling should stay in place.

I’m having this issue as well, I was able to solve it in the case of simple paths like icons, by setting every layer to ‘Scale’. But it doesn’t work with text layers.

It automagically fixes itself as soon as you detach the component or simply select the layer in the main component (if it’s a Local Component), so it’s definitely a bug. 🐛

I was having a similar issue with nested variants. I have:

Component 2 [ Variant 2.A(Variant 1.A), Variant 2.B(Variant 1.A), … ]

where the variants of component 1 are different sizes and scales.

Replacing Variant 1.A within the master component for 2 scaled properly, but not when I replaced it in component 2.

I was able to resolve this by going to Component 1 and adding auto layout to all the variants. This yielded correct scaling in the instances when the variant was switched out. I don’t know if this will work with variants, and I don’t know why the auto layout I had on the components before combining into variants didn’t carry, but it’s worth a shot.

(I found this thread from another one and thought I’d post my solution here as well)

I’ve had some similar issues with swapping variants. I was able to resolve it by adding autolayout to all my variants. I don’t know why autolayout didn’t carry over when I made the components in the first place, but adding it back fixed it.

It’s not quite the same thing as what you’re talking about here, but I figure checking autolayout is worth a shot!