You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting with a basic setup of (A=1B=3) -> MAX -> watch - the numbers are actually added together and we get 4
If we manually change the OP to min, we get the expected value of 1
Then manually changing back to max we get the corrected max value of 3
This applies to all of the basic math nodes, such as * or - - the initial output is always addition (examples shown are both fresh graphs without manually changing the OP property):
Playing around with some breakpoints in the example project, it seems that since the operation's _func is not set until MathOperation.prototype.onPropertyChanged is called, the default _func of MathOperation (which is return A + B) is used even though the node added was a MIN/MAX node.
The text was updated successfully, but these errors were encountered:
Starting with a basic setup of (
A=1
B=3
) ->MAX
->watch
- the numbers are actually added together and we get4
If we manually change the OP to
min
, we get the expected value of1
Then manually changing back to
max
we get the corrected max value of3
This applies to all of the basic math nodes, such as
*
or-
- the initial output is always addition (examples shown are both fresh graphs without manually changing theOP
property):Playing around with some breakpoints in the example project, it seems that since the operation's
_func
is not set untilMathOperation.prototype.onPropertyChanged
is called, the default_func
ofMathOperation
(which isreturn A + B
) is used even though the node added was aMIN
/MAX
node.The text was updated successfully, but these errors were encountered: