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

Plan view in a Time Strip does not react to resize events #7971

Open
2 of 7 tasks
charlesh88 opened this issue Dec 20, 2024 · 0 comments
Open
2 of 7 tasks

Plan view in a Time Strip does not react to resize events #7971

charlesh88 opened this issue Dec 20, 2024 · 0 comments

Comments

@charlesh88
Copy link
Contributor

charlesh88 commented Dec 20, 2024

Summary

The Plan view must recalculate activity and event positions and wrapping when the viewport width changes. This is handled properly in the Plan and Gantt views, and works when a Plan or Gantt is within a Flexible Layout, but not when either of those views are in the Time Strip view.

Plan in Time Strip not reacting as expected
Screenshot 2024-12-19 at 4 20 47 PM
Screenshot 2024-12-19 at 4 20 40 PM

Expected vs Current Behavior

Width change events in the Time Strip view must be handled by the Plan view.

Plan view reacting properly
Screenshot 2024-12-19 at 4 20 12 PM
Screenshot 2024-12-19 at 4 19 47 PM

Steps to Reproduce

  1. Go to a Plan view that has activities in a known timeframe, or create a new Plan. Some import-ready Plan data is here: Synth plan 2024-12-19.json; set your time coordinates to a fixed interval around 12/19/24.
  2. Save, then change the view area width by dragging the Inspector pane edge about. Also resize the browser window.
  3. Observe: the Plan will react, scaling activity bars, updating bar X positions and reflowing vertically when needed.
  4. Put the Plan into a Time Strip (TS) view.
  5. Repeat step 2.
  6. Observe: the Plan will not scale activities, update X positions or reflow.

Environment

  • Open MCT Version: 4.1.0-next
  • Deployment Type: shared NASA server
  • OS: doesn't matter
  • Browser: you choose

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