[2.0.66] Decider combinator does not highlight true Each condition

[Etherblood]

What did you do?
I attached a [9 stone red] input to a decider combinator and set its condition to [Each=9]. It had no other inputs.

What happened?
The condition was not highlighted, but it still had a [9 stone] output, meaning the condition correctly evaluated to true.

What did you expect to happen instead? It might be obvious to you, but do it anyway!
I expected the condition to be highlighted in the GUI since the condition evaluated to true for each signal.

Does it happen always, once, or sometimes?
A condition of [stone=9] in the above case is highlighted as expected.
The [Each=9] condition is also not highlighted when the input is [6 stone red] + [3 stone green]. A [stone=9] condition is highlighted as expected for this case too.
I tried multiple different signal types all with the same result.

[boskid]

Thanks for the report however i am going to classify this as a Not a bug. Current design is that when a condition involves signal "Each", then we do not perform highlighting because the exact highlighting depends on the exact substitute signal for which a condition is being evaluated, and as such the highlighting only becomes effective when you hover cursor over one of the input signals. I suspect you are considering condition with "Each" to become true in itself using a normal interpretation of a word "Each", however we defined "Each" to be working as a vector operator, allowing decider to evaluate conditions independently for each of the input signals. If you want a condition that is true when all signals on the input side pass the condition, then please use an "Everything" special signal instead.

[Etherblood]

Okay, thank you.