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
When code is decompiled back to blocks by the emitter the '-=' operator is not supported,
e.g.
material.roughness-=myroughness
becomes,
Similarly using a negative operand with the '+=' operator we get an interesting round-trip,
material.roughness+=-myroughness
becomes,
and then when switching back to code,
material.roughness+=0-myroughness
If we introduced a negative block that would return negated numerical input we could special case this block in conjunction with the change block as its parent to compile/decompile to/from the '-=' operator and its associated expression.
The text was updated successfully, but these errors were encountered:
I guess I missed that operator. We should indeed discuss having a negation block, but that's a separate issue from this. I'll add support to -= with our existing 0 - x decompilation hack
(really an improvement more than a bug)
When code is decompiled back to blocks by the emitter the '-=' operator is not supported,
e.g.
becomes,
Similarly using a negative operand with the '+=' operator we get an interesting round-trip,
becomes,
and then when switching back to code,
If we introduced a negative block that would return negated numerical input we could special case this block in conjunction with the change block as its parent to compile/decompile to/from the '-=' operator and its associated expression.
The text was updated successfully, but these errors were encountered: