beyond confused with equal node

[mowgli]

With the patch shown below, I would've expected Equal to only output something when the left =1.
Whatever I've tried, it outputs a trigger on every single Bar click, independently of whether left and right are equal or not. Hovering over the output reveals the correct True/False statement though. The trigger going through is reflected in both Trigger and Boolean nodes.

The Boolean node is sent to event. My understanding is that event will only pass something through when the value changes yet it's passing something through constantly, even when the value is constantly False.


I'm confused beyond belief. What am I missing?

[mowgli]

Ok.
I've fixed it by putting an IF after the equal, but I still don't fully understand how it all works.

From the training videos, a Boolean set to event shouldn't be outputting anything unless its input value changes.
Receiving False repeatedly does not count in my book as a value change.
Can anyone explain to me the logic behind all this?

[tijnisfijn]

just put a on change behind it that would solve it it think...

[mowgli]

Thanks for your help.
In any case, I'm trying to understand what is actually going on as this behaviour makes no sense to me. Can you shed a light?
It looks like there is more than one signal travelling through the node. One is the Boolean true/false, but there's also a trigger of sorts going down the same wire.

[tijnisfijn]

Every time a signal reaches the equal note it gets compared and it will send a true or false message even if the signal before was also true or false it will send this for every signal it receives. And because both true and false are a event it will still send a event/trigger on every signal received. The easiest way to circumvent this is to put a on change node after it it will only send Events if there is really a change in the incoming signal so multiple events of the same kind will be ignored. I hope I explain this correctly and it will help you out.

[subpixel]

The description I came up with re the different flows is that the difference is only *when* the data is delivered.

The "If" node is confusing! It feels like using RPN (Reverse Polish Notation).

Comparison produces a bool (t/f). Every frame for a "signal". On "(re-)compilation"/start for an "attribute". I'm not sure if there is event-input comparison, but if there is, it will only emit a bool when an event input arrives.

An "On Change" node is required if you only want to emit an event once when the input value changes. At that time the input *value* is emitted as an event. Maybe true, maybe false. If that is connected to an input "button", it is likely that both true and false will press the button, because the button only cares that an event (or "bang!") has occurred.

Suppose you only want action when a bool event arrives and the *value* is true. The IF node receives the event, and emits the event only out of one output, the "True" output if value true, th4 "False" output if value false. It makes sense ti think of the IF node as an event router.

-subpixel