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
Resolve global scope correctly in SolverManagerFacet
When MODIFY is parsed inside a non-global scope (e.g., MODIFY:Face on a
SIZE object), VarModifier.getLegalScope() reports the parsing scope, not
the variable's actual scope. Following that path produced a ScopeInstance
that did not match the one used when reading the variable, so modifiers
were applied to a different VariableID than channels read from.
Routine the scope through resolveScope(): if the parsed scope is global,
or if the variable is legally defined at the global scope, use the global
ScopeInstance. Otherwise fall back to the local scope as before.
Fixes the Pathfinder FACE tests (which use MODIFY:Face on SIZE objects
to set the global Face variable to "5,5") and the GlobalModifyTest
identity-mismatch failures.
0 commit comments