Invert boolean variable for layer display

Yes, I’ve just encountered this too. I wanted to have a button that would show a message on click and hide a panel at the same time. I ended up instead showing a layer over the panel I wanted to hide. So basically, showing some things that hide other things. A bit klunky.

As an aside, I do find it a bit awkward having everything in variables. Things get quite abstract quite fast. So “On click, set Boolean [name] to true” and then have to keep track of what things use that Boolean. Would be nice if you had the option to have common operations like hide/show explicit if you wanted. So eg “On click, show [objectA], hide [objectB]”. Or “On mouse in, set [objectC] to [StateX]” But hey.

@Alex_Cowley,

This feature is sorely missing - its UI could be as simple as an inversion checkbox in the boolean property editor.

The above workaround does not remove elements from a frame’s auto-layout flow the way hiding does. Inverted booleans would enable much more meaningful structural variation in components.

Could be really useful. Right now I just create two booleans for such cases. Which results in more work during interactions setup

As Daniel said above, an inversion checkbox in the boolean property editor. Please!

it works for self-rolled basic shapes and things but when I try with more complex components, unfortunately they just vanish, but for shapes and things it’s good to know, I don’t see any other solutions out there. Thanks.

It would also be useful if you could bind the layer show/hide state to an expression. Then you could set it to “not $YOUR_VARIABLE”.

The feature to invert boolean variables would be real nice. Also currently working around by having two boolean variables for each visibility usecase and just taking care where and when to use what of these. Gets confusing after a while, but works, tho.

I’ve had to do this too. Feels redundant, and adds more complexity to the prototype.

We need the ability to hide a layer when a boolean is set to true.

Also looking for this option. It would save me from making lots of redundant boolean properties or variants in my design system file.