Receiving a message, and then assigning a value and then writing a conditional based on that value is that something that is quite a normal, conceptual pattern – but in Protopie it will often not work as expected. This is because responses to Protopie triggers all happen simultaneously and not in the order written.
Even all-Scenes variables are not accessible inside a component. And this can lead to hard to find errors when a variable with the same name is used in a component, but its value is not sync’d with the scenes.
parseJson is.a very useful and powerful function, but it doesn’t do all you might expect of it (yet, hopefully).
This pitfall is not a big deal, but it can waste you time as you try to track down why your variable seems to have the wrong value (or no value). It can also bite you in a formula where your variable is of the wrong type for the formula.
Most prototyping tools for designers use the frame-by-frame, or multiple dartboards model. But Protopie is much closer to a developer’s object-oriented model of an application UI.
This is a very easy mistake to make – sending a message to be picked up by a component, but one that you have in fact placed into a different scene. Although you can send to a different pie, you can’t send to a different scene.
You can send messages in different ways, but Protopie requires you to receive them in the matching way. A common (and easy) mistake is to send a message to a ‘parent’ while wanting to receive it from the current scene.