Fix moh reset button in fault tree editor #626
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@blcham
Fix #593
Fixes behavior of MOH input field and its refresh button.
The screen shots below show how the MOH input field is rendered based on three variables,
MOH
),ftMoh
) andsMOH
).The style of MOH field uses orange color for the value of the MOH filed to distinguish if
MOH
is different fromsMOH
and orange color to of the border of the field to distinguish ifMOH
different fromftMOH
. The field also has localized hint(s) to show1) MOH = ftMoh and MOH = sMOH
2) MOH != ftMoh and MOH != sMOH
- e.g. user updated MOH the value in the field3) MOH = ftMoh and MOH != sMOH
- e.g. user evaluated tree with MOH != sMOH4) MOH != ftMoh and MOH = sMOH
- e.g. user updated MOH to be equal to sMOHThe reset button updates the MOH value. Note that the reset button does not persist MOH (i.e. does not set ftMOH by calling server api) and it does not evaluate fault tree with MOH. The reset button works as follows based on the current state MOH, ftMOH and sMOH:
1) MOH = ftMoh and MOH = sMOH
2) MOH != ftMoh and MOH != sMOH
or4) MOH != ftMoh and MOH = sMOH
3) MOH = ftMoh and MOH != sMOH
User