-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conditional set output is wrong #6244
Conversation
Here's the new behavior: Screen.Recording.2023-02-01.at.1.22.18.PM.movI'm turning of YAMCS data to simulate the "no data" situation, then starting YAMCS to show the ConditionSet receiving data. It also works if you create a Sine Wave Generator with a loading delay. If this looks good, I'll add an e2e test with a Sine Wave Generator that has a loading delay. |
Codecov Report
@@ Coverage Diff @@
## master #6244 +/- ##
==========================================
+ Coverage 53.33% 54.91% +1.58%
==========================================
Files 626 626
Lines 26617 26617
Branches 2403 2403
==========================================
+ Hits 14195 14616 +421
+ Misses 11758 11341 -417
+ Partials 664 660 -4
*This pull request uses carry forward flags. Click here to find out more.
... and 71 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
https://www.w3.org/WAI/ARIA/apg/patterns/accordion/ is a good guideline for the rules within the condition set. Mainly isExpanded and button |
…a/openmct into 5918-conditional-set-output-is-wrong
@scottbell @charlesh88 If you drag the condition set with output ConditionSetDefaultOutput.mov |
Be sure the Sine Wave Generators you're testing with have a somewhat low frequency and substantial delay. Also, changing the delay of a Sine Wave Generator necessitates a page reload (from what I can tell): Screen.Recording.2023-02-06.at.11.23.10.PM.mov |
@shefalijoshi @charlesh88 Regarding the difference between DisplayLayouts and the ConditionSet view on historical data, this appears to be a pre-existing issue in Screen.Recording.2023-02-07.at.2.25.27.PM.movNamely, the ConditionSet view only updates if it's Local Clock mode: Screen.Recording.2023-02-07.at.2.26.50.PM.movI've got something cobbled together to fix the historical data issue here. From what I can tell, the "Test Data" also only seems to work in Local Clock mode. Is that expected? Screen.Recording.2023-02-07.at.3.55.27.PM.mov |
In testing this I found a weird edge-case, which I will file a followup for because I think it's actually a long-standing issue with conditional styling and not an issue with condition sets themselves.
|
Filed #6444 for the followup issue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm now seeing composition problems. Specifically:
- Make a new Condition Set (CS).
- Add telem to it (sine wave gen). Define condition(s).
- Save and exit editing.
- In the tree, expand the CS.
- Use the "Remove" action to remove the telem element. The element will appear to be removed. The CS outputs "---" but incorrectly highlights the Default condition.
- Collapse the CS in the tree, then re-expand it. Note that the telem element returns, and is clickable/navigable. The CS is not evaluating, and displays "---".
- Edit the CS, note that the telem element appears in the CS's Elements pool and the CS does not evaluate it.
I tested this with another domain object (Gauge) and did not see the same issue. No console errors were thrown during the above sequence.
@charlesh88 I think the composition issue is separate from this PR, in that the behavior is also happening in Screen.Recording.2023-03-16.at.6.51.17.PM.mov |
Tested before that other recent PR in, and it looks like this bug predates that too. |
@charlesh88 talked to @akhenry about this, and we've filed a separate issue for the tree composition problem. Regarding this:
I'll look into it for this PR. |
@charlesh88 The current condition should be getting cleared now when there isn't telemetry: Screen.Recording.2023-03-17.at.1.26.16.PM.mov |
Closes #5918
Describe your changes:
All Submissions:
Author Checklist
Reviewer Checklist