Same.
Seems like it would be of great benefit to have the variants (as they are today) but then have the ability to override those variants with variables when creating a prototype.
As it stands now, I am having to break components apart to access the various elements within so that they can be controlled by variables. It’s making a mess of my files and destroying the power of having a component library.
Hey Friends,
I have created a plugin that can help with packaging components and component sets (variants) with variables, and enabling insert of such as component sets, components and instances with variables still attached to their source (global) or cloned as local variables.
Check it out at Figvar.com or just search for the Figvar plugin.
Cheers,
Martyn
Please support assigning a variable to an exposed property in a component. In Microsoft, components are heavily used in design deliveries between disciplines. An example would be from UX to CX (Writer). Being able to assign a variable to an exposed property in a component, especially when multiple instances are used, dramatically reduces the amount of laborious work to manually update all the instances.
I see that similar requests have been submitted as early as 2022. I was wondering the reason this is not supported. Thank you!
Wasn’t this obvious from the start?!!! It’s been more than 1 year since variables are released and this MUST HAVE feature isn’t available yet? How can it be? And all we get is new UI, which btw makes it harder to access basic features. :///