When I assign an action to a nested instance in a component which sets a variable it doesn’t seem to work. The component’s variant changes, but the variable is never changed. There are no warnings or errors.
When assigning the same action to the outer component it does set the variables.
Figma, Variables is a great idea and a step forward, but in its current state it’s very limited so much that it misses the point. For example, using variables and the new ‘wrap’ auto-layout, I managed to reduce 8 component variants to 1 frame. But, I am not able to turn this frame into a component since it contains two (nested) components, to which I wanted to be able to assign a variable to auto set THEIR selected variant… I know this is confusing, but the point is, VARIABLES should work EVERYWHERE, including nested components, otherwise in many cases it’s unusable. Is there a plan to fix this in the future?
Also, this does not seem to work on non-component, nested frames. I was attempting to create a drop-down list to filter search results and none of the interactions on the nested frames (list items) were getting triggered. FYI, I was only using Set Variable with each of the interactions.
this is a really unfortunate issue. The nav 2 and nav 3 switch back to the Nav 1 title when using the variable to control the state: (on mouse down, set the variable of the state of nav2 and nav3 to default) - any way around this?
Also should mention, after buttons 2 and 3 switch to the language Nav 1, if i mouse over those buttons they do go back to the Nav 2 and 3 titles, its the initial state that goes back to the original instance labels
thanks for any help on this...
When I assign an action to a nested instance in a component which sets a variable it doesn’t seem to work. The component’s variant changes, but the variable is never changed. There are no warnings or errors.
When assigning the same action to the outer component it does set the variables.
Figma, Variables is a great idea and a step forward, but in its current state it’s very limited so much that it misses the point. For example, using variables and the new ‘wrap’ auto-layout, I managed to reduce 8 component variants to 1 frame. But, I am not able to turn this frame into a component since it contains two (nested) components, to which I wanted to be able to assign a variable to auto set THEIR selected variant… I know this is confusing, but the point is, VARIABLES should work EVERYWHERE, including nested components, otherwise in many cases it’s unusable. Is there a plan to fix this in the future?
thank you! Thank you!
Also, this does not seem to work on non-component, nested frames. I was attempting to create a drop-down list to filter search results and none of the interactions on the nested frames (list items) were getting triggered. FYI, I was only using Set Variable with each of the interactions.
this is a really unfortunate issue. The nav 2 and nav 3 switch back to the Nav 1 title when using the variable to control the state: (on mouse down, set the variable of the state of nav2 and nav3 to default) - any way around this?
Also should mention, after buttons 2 and 3 switch to the language Nav 1, if i mouse over those buttons they do go back to the Nav 2 and 3 titles, its the initial state that goes back to the original instance labels
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
