Improve implementation of Freeze
and Release
#3829
Labels
category:codebase:handle
relating to handles or handle types (BinaryValue)
type:bug
a bug in existing functionality
Currently, these actions are implemented using the same mechanism as regular value sets. They first sample the current value and then use then as the value in their "set". This overwrites other explicit writes with the implicit write the implementation does. This is surprising behavior and should be avoided.
If you update a value and then immediately do a
Freeze
, it will freeze the current simulator value, not the value just scheduled.Or if you do a
Force
followed immediately followed by aRelease
you get the same issueThe text was updated successfully, but these errors were encountered: