Use inverse of Boolean variable to show/hide layer

Every time I play with variables I find limitations like this and end up dropping the entire experiment in favor of more explicit states. So, if you want people to actually adopt variables, especially in prototypes, maybe support more than trivial examples?

Not having this really basic functionality makes boolean variables just about useless. Nearly always when not-showing something, something else should be show.

Not having this this also makes prototype logic unnecessalily complex. Most booleans need an inverse and both need to be constantly set separately. Even when just one boolean will work, it must work on logic that may not make sense in the context of the prototype.

Yes this is so annoying - I have so many prototypes that have like 48 variables when I could do it with 12 if only the booleans were reversible.

Chiming in here to say I REALLY need this too 🥲

It felt odd that it was not implemented from the start.

It became ever more odd after the launch of variables expressions: https://help.figma.com/hc/en-us/articles/15253194385943-Use-expressions-in-prototypes
because it affected (in a good sense) the prototyping, but left Designer UI far behind.

Currently if a user wants to use a boolean variable, they have to create TWO of them:

So every Foo var should have aNotFoo mate that is just… a negation of the former.

Not only it doubles the amount of variables, it also doubles the complexity of all interactions: when you set Foo=true, you have to not forget to set NotFoo=false as well.
And since it’s not constrained by anything, designer has to manually watch them to be in sync.

So these two things are highly awaited:

1. Variable VALUES should allow for expressions

Instead of “String value” we need expressions.

2. Variable USAGES should allow for expressions.

In addition to “Search” we need expressions.

Yes, I need this too, but more than just reversing I’d love to be able to use multiple variables, like:
Show layer if BOTH Variable A and B are true AND variable C is false.

I need this too!! 🙏

+1 
Came here just to see if anyone else was having this same annoyance. Glad its not just me!
Really would like to see this as a simple UI toggle where its needed to save on the increasing number of its on/its off booleans.
Please Figma, hear our cries for this, it would be really powerful and cut a lot of extra work out of our daily lives aka : High Impact, Low Overhead easy win for Figma Crew!

Thanks ​@Thomas_Nabelek & others for adding to this.

Same problem. This would reduce my prototyping time to half of it. 
Please add this feature.

+1 This is quite a pain to not have this feature