Hello, everybody!
I faced some weeeeeird behaviors last night. I fixed that problem for one file, but when I tried to make a new one in order to reproduce the workaround, that didn’t work.
I wanted to make a dialog pop-up, where users could chose an option that would reflect in the main screen (imagine a MFA screen, where the user can change the channel in which they’d receive the code).
The bug is that the options just doesn’t update correctly:
What I did to fix the problem in the original file, was to create a duplicate of the variable and use that duplicate to update the original variable.
So, in the interactions I’d do something like this (I’ll be using some pseudo code syntax here):
On Click () { var1 = var2 }
But that var2 would actually contain the Mode I wanted, so something more like:
On Click () { var1 = var2:modeA }
In the file I’ve uploaded, though, that workaround did not fixed the problem (as seen in the gif). It looks like the action of setting the variable do nothing, or that the variable is getting some cached value from somewhere else.
Phantom Variables.fig (35.7 KB)
NOTE: I also tried to reproduce with no success a “phantom variable” I got in the og file. That happened when I deleted a variable and created another one with the same name, but different content in each mode. When I tried to update the link between the text layer and the variable, one of the layers didn’t show the (?) thing from a deleted variable. Instead, it showed it active, without the (?) mark, and with the old content.
Did anybody faced something similar to this?
