Skip to content
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

Plots are respecting independent time context settings, even if not enabled #7737

Open
7 tasks
davetsay opened this issue May 23, 2024 · 0 comments
Open
7 tasks

Comments

@davetsay
Copy link
Contributor

davetsay commented May 23, 2024

Summary

If you are viewing a plot in realtime mode, pause the plot, then sync the time conductor, Open MCT will prompt you to accept that time conductor will be changed to Fixed time mode. If you have an independent time context and it is in fixed time mode (an assumption because it has never enabled in this use case), but it is not enabled, you do not get the warning message and you are switched to fixed mode in the time conductor. Furthermore, if you use independent time context and pause then sync time, it works, but the UI isn't completely reactive to that change, the independent time context appears to be in realtime mode still when in fact it has switched to fixed.

I assume many other things doing checks or actions on this.timeContext are similarly affected.

Expected vs Current Behavior

Steps to Reproduce

No fixed time change warning prompt

  1. Create an overlay plot and add telemetry to it (sine wave generator)
  2. View the plot in realtime mode
  3. hover over the plot and click Pause
  4. hover over the plot and click Synchronize with Time Conductor
  5. Observe you do not get a warning message and are switched to Fixed time mode
  6. Repeat steps 2-5 but with the sine wave generator instead of the overlay plot
  7. Observe with the sine wave generator without a timecontext toggle, you do get the warning.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants