Plot view cursor guides in Time Strip views don't work

[charlesh88]

Summary

Currently, the cursor guide button in embedded plot views in a Time Strip is available and clickable, but the guides are confined to an individual plot element and don't work at all. Guides do follow the cursor in Stacked Plot views.

Cursor guide button appears on hover

Cursor guides are shown but don't follow cursor

Expected vs Current Behavior

There are a number of acceptable ways to fix this:

1. BEST: Implement a cross-all-swimlanes cursor guide solution. Similar to how Stacked Plots work now, invoking cursor guides in one nested plot view enables them in all, but this enhancement makes the guide extents visible in all plot views at once, with data point hovering occurring in all plot views.

** Spanning cursor guides in a Stacked Plot view**

This however, is complicated in a Time Strip view, which allows Stacked Plots to be embedded as a child element, in effect allowing a stacked item within a stacked view. The cursor guides would have to allow for this situation and function across all stackable contained objects. Additionally, independently zoomed or panned plot views would have to be accounted for, ideally by properly calculating the guide position in relation to a a view's zoom or pan settings. If we go this route, a separate issue should be filed for this and it must be implemented in Stacked Plots as well.
2. GOOD: At least make them work the same as they do in Stacked Plots, with the guides enabled for all contained plot views, but only displayed within each at a time.
3. ARGH: Suppress the cursor guide button for plot views in a Time Strip. We should only do this if #2 is out of scope.

Steps to Reproduce

1. Add plottable views to a Time Strip.
2. Click a plot view's cursor guide button.

Environment

• Open MCT Version:
• Deployment Type:
• OS:
• Browser:

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