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
Because Condition Sets (CS) only output when they receive data, it becomes impossible to apply styling to an object when using Conditional Styling and no data is available to the CS. Steps to reproduce makes this a little more clear below.
Expected vs Current Behavior
For objects that use conditional styling, the user must have a way to set a desired style that is applied when no data is available to trigger a Condition Set's condition. This is especially important where things like large font sizes and background colors are desired.
Steps to Reproduce
Make a Condition Set. Don't include any data sources, and you don't even have to add a condition. Save it.
Make a Display Layout, then use that CS to conditionally style something like an alphanumeric or a drawing object in the layout. Make sure to set fill and stroke for the default condition (or even better, visibility). Save and exit the layout.
Nav away and back to the layout, and observe: the styled object will appear with whatever it's baseline "system" default style is, and will not use the conditional's default condition styling.
Proposed Solution
Apply the default condition style in the case where the Condition Set isn't outputting anything. Note that I do NOT think that Condition Sets should be changed to always output their default value in the absence of a triggering input.
Environment
Open MCT Version: 2.1.2
Deployment Type: local, servers
OS: all
Browser: yes please
Impact Check List
Data loss or misrepresented data?
Regression? Did this used to work or has it always been broken?
Is there a workaround available?
Does this impact a critical component?
Is this just a visual bug with no functional impact?
Does this block the execution of e2e tests?
Does this have an impact on Performance?
Additional Information
The text was updated successfully, but these errors were encountered:
This has regressed and is currently broken: a conditional styling's default style is not being applied as expected when no data is available. Additionally, the Inspector highlights that style as if it's being matched and output, which is also incorrect behavior.
This example uses a Condition Set with no telemetry added to it; I also tested by adding an end point with no data, with the same result.
The fix, again:
When using Conditional Styling, apply the default style in all cases unless the Condition Set in use is getting data and matches a condition other than the default.
The default style should not highlight in the Inspector, even when it's "being applied". This is not a critical change, but could be misleading, as if that condition was being matched and was being output by the Condition Set, which is not the case. In the example below, the Condition Set's view in browse mode is what's expected for the current case.
@charlesh88 Let's sync on this next week. To me, this is conflicting with the requirements previously stated here and the work done to separate the concept of a "default value" from "no value".
Summary
Because Condition Sets (CS) only output when they receive data, it becomes impossible to apply styling to an object when using Conditional Styling and no data is available to the CS. Steps to reproduce makes this a little more clear below.
Expected vs Current Behavior
For objects that use conditional styling, the user must have a way to set a desired style that is applied when no data is available to trigger a Condition Set's condition. This is especially important where things like large font sizes and background colors are desired.
Steps to Reproduce
Proposed Solution
Environment
Impact Check List
Additional Information
The text was updated successfully, but these errors were encountered: