Skip to main content
Participant
August 25, 2020
Answered

Saving toggle settings so when I change pages it remains the same

  • August 25, 2020
  • 1 reply
  • 412 views

Hi, I am currenly designing a checklist app and have animated the tick so it can go on and off. BUT everytime (in prototype mode) when i check the box then go to a different page on the app then back, it has gone back to its original state. I really want to fix this. Pls can someone help!

This topic has been closed for replies.
Correct answer Spas K.

Unfortunately, there is no way for you to retain a component's changed state after you switch to another screen. It's just how it works. Every time you load a different screen, all the components on it will be reset to the state that they were originally exported as on that screen.

 

With the way prototypes work, they don't retain or collect any data from the user. They are pretty much a bunch of images, but don't have any dynamic functionality behind them. There is no "database" to store the state of the component. It just works for the current screen, and that's it. There are a few feature requests on uservoice about conditional logic, but I think that's quite far on the dev team's roadmap.

 

For now, the only way to achieve what you want would be by using a different artboard, where the checkboxes are selected by default, and link to that after the second screen. Ofcourse, covering all the cases of what's checked and what isn't might not be practical. 

1 reply

Spas K.
Community Expert
Spas K.Community ExpertCorrect answer
Community Expert
August 25, 2020

Unfortunately, there is no way for you to retain a component's changed state after you switch to another screen. It's just how it works. Every time you load a different screen, all the components on it will be reset to the state that they were originally exported as on that screen.

 

With the way prototypes work, they don't retain or collect any data from the user. They are pretty much a bunch of images, but don't have any dynamic functionality behind them. There is no "database" to store the state of the component. It just works for the current screen, and that's it. There are a few feature requests on uservoice about conditional logic, but I think that's quite far on the dev team's roadmap.

 

For now, the only way to achieve what you want would be by using a different artboard, where the checkboxes are selected by default, and link to that after the second screen. Ofcourse, covering all the cases of what's checked and what isn't might not be practical. 

Participant
August 25, 2020

Spas K. 

 

Thank you so much for replying. Ok, I'll hav to do it that way! That's gonna take forever!!! 

Thanks again

H