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
Switching a comparison data type should result in changes to the dataclass.
In some senses I am in favor of the current behavior, unless you actually change the value you shouldn't modify the dataclass. But when you change to an enum, a value is filled. It would be unintuitive in this case for ATEF to not apply this value to the dataclass
Current Behavior
If you switch a comparison's data type from e.g. float to enum and leave the combobox alone, it doesn't actually edit the dataclass in such a way to save a change. You have to manually re-select e.g. FALSE again. (Found because my test case was failing on 0.0 != 0/FALSE)
Expected Behavior
Switching a comparison data type should result in changes to the dataclass.
In some senses I am in favor of the current behavior, unless you actually change the value you shouldn't modify the dataclass. But when you change to an enum, a value is filled. It would be unintuitive in this case for ATEF to not apply this value to the dataclass
Current Behavior
If you switch a comparison's data type from e.g. float to enum and leave the combobox alone, it doesn't actually edit the dataclass in such a way to save a change. You have to manually re-select e.g. FALSE again. (Found because my test case was failing on 0.0 != 0/FALSE)
Possible Solution
Fill the values when the type changes
Steps to Reproduce (for bugs)
See current behavior
Context
#241
Your Environment
pcds-5.8.4
The text was updated successfully, but these errors were encountered: