Skip to main content
Question

State management doesn't show options

  • December 8, 2023
  • 4 replies
  • 1071 views
L

Hi! Iā€™m having a problem with the state memorization. I want a component to keep the same state when re-opening the frame. I looked it up and in their article here it says ā€˜ā€˜When you navigate back and forth between frames, objects re-open in their last set state.ā€™ā€™ (related article)

But in my case, the state management only shows one option: ā€˜ā€˜Reset scroll positionā€™ā€™. It doesnā€™t show ā€˜ā€˜Reset component stateā€™ā€™ or other options. The article says to update to new state management via the update button, which doesnā€™t show for me. Also, Iā€™m pretty sure I have the latest update installed.

Can someone tell me what I have to do to use component states?

This topic has been closed for replies.

4 replies

J
Figmate
  • Junko3
  • Figmate
  • December 11, 2023

Hey there, Thanks for reaching out about state management, and appreciate you checking our article!

The reset settings only appear if they are relevant to the currently selected interaction. For example, if the interaction connects to a frame with interactive components, the ā€œReset component stateā€ option is available.

Screenshot 2023-12-11 at 15.50.06

Hope it helps! If it doesnā€™t could you please demonstrate your current setup in a quick screen recording and share it? This way, we can take a closer look!

Thanks,

Shukri_Brewer

ā€œReset component stateā€ does not show for me on a button where the interaction is to open an overlay. The issue I am hoing to resolve is that the button gets stuck in ā€œpressā€ state, and does not reset after the overlay closes

djv
Figmate
  • djv
  • Community Support
  • March 15, 2024

Hey @Shukri_Brewer,

Thatā€™s odd. Are you able to share a screenshot or a link to your file, so we can see whatā€™s happening on your end?

If you decide to provide a link, please also share it with support-share@figma.com, so we can take a closer look.

Benoit_VICENTE

Hi. I have the same issue. Did you solve it ?

Terms & ConditionsAccessibility statement