allow us to set booleans in expressions

[F3der1co]

Reviewed guidelines

• [X] I have read and understand the suggestion guidelines

Checked for duplicate suggestions

• [X] I checked for existing similar suggestions

Summary

Allow us to set booleans in expressions. Only being able to set booleans via their specific conditions is limiting, it doesn't allow using conditionals to set it or other dynamic systems.

Possible workarounds or alternatives

Using a number variable set to 0 or 1. But it doesn't enforce the value actually being 1 and 0 and can be less explicity which is particularily bad in projects whit multiple developers.

Proposed solution

Allow us to set booleans via an expression (using truthy and falsy value check). Imo they could just be added to set variable, but alternatively a new action set boolean by expression could be added.

Why is this idea important?

more flexibility and ease of use

Additional remarks

No response

[dop2000]

To add to this suggestion - setting boolean in an expression is only a small part of the problem. We should be able to freely use boolean variables in expressions.

Also, please add boolean expressions - obj.IsVisible, obj.CollistionsEnabled, obj.Behavior.IsEnabled, layerIsVisible etc. Currently these checks are only available as conditions, they break the flow of events and make the code a lot more fragmented and entangled.

[F3der1co]

We can already use boolean variables in expressions. While I agree that having some conditions/properties available as booleans in expressions would be handy, it is something way more nuanced/complex while this one is a lot more straightforward, so I would say this makes more sense as a separate suggestion.

[dop2000]

We can already use boolean variables in expressions.

Oops, maybe they were not working in C2? To be honest, I never use booleans in Construct because it's such a pain.