I am looking for the availability to HIDE a layer when a Boolean variable is TRUE and SHOW it when it is FALSE. So, the inverse of the default/current behavior. I want to do this without using components.
Use case: When a variable is true, show one frame. When that same variable is false, show a different frame.
I can get basically this by using two different variables:
but it would be more convenient to be able to do it with just one. Just give me a Boolean toggle when the variable is used to say if the variable should be inverted or not.
I have a checkbox that turns the container on and off on the layout.
Right now I have one variable used to switch the checkbox and the other to display the container
For example:
clicked on the checkbox - the jackdaw is enabled, the container is hidden
, clicked again - the jackdaw is missing, the container is shown
Currently, 2 variables are used for this. I really want to be able to see when the layer is displayed: if true, if false
It seems to me that you had something similar. Maybe it can be simplified somehow? I will be glad to help!)
I am building a fairly complex app.
To manage the state of the panels, I rely on the Layer Visibility with booleans. I have to set up almost every booleans twice, like:
is_EditModeActive?
is_EditModeInactive?
Then I need A LOT of conditional branching and twice the amount of “set variables” to achieve what I need.
A simple custom variable defined like is_EditModeInactive? = !{is_EditModeActive?} or a simple “boolean inverter” while right-clicking the “Eye” icon at the Layer level will make complex work WAY easier. Now it’s a nightmare for advanced prototypes.
Need this ability really.
Spent almost half day trying to hide/unhide multiple layers based on simple interactive checkbox component.
Tried different IF ELSE conditions with my interactive checkbox component which has got two selected states (yes/no), but the ELSE condition, set up set the values of couple of other Boolean variables to true/false, simply does not get triggered at all. The first set of conditions work which are in the IF part.
(I figured its happening because in essence the second checkbox “click” is actually happening on Variant state B of the instance, while the conditional statements are defined “on click” of the variant state A!)
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.
