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
Go to a Plan View (like this one) with the Time Conductor in RT mode. If the plan doesn't have dates within the current time bounds, you should see something that looks like this:
Change the TC to Fixed Time Mode and enter a start and end that encompass the plan's extents. If using the plan linked in this issue, set the End to 2024-03-22 07:00:00.000Z and then the Start to 2023-12-21 12:00:00.000Z. Tabbing out of either TC input should have refreshed the plan view, but it doesn't.
Now, resize the browser window or resize a pane in Open MCT. Observe: the plan will now refresh and be displayed properly:
Notes
When the Plan view is in a Display Layout, pane and browser window resize events don't force an update, presumably because the size of the plan container hasn't been affected.
This problem also occurs when interacting with the TC's History menu.
When making changes to the time bounds in the TC, this console error is being thrown:
The text was updated successfully, but these errors were encountered:
charlesh88
changed the title
Plan View/Timestrip not hearing Time Conductor bounds changes
Plan View/Timestrip not responding Time Conductor bounds changes
Jun 14, 2021
charlesh88
changed the title
Plan View/Timestrip not responding Time Conductor bounds changes
Plan View/Timestrip not responding to Time Conductor bounds changes
Jun 15, 2021
Testing instructions:
Create a conditionset with at least one condition other than default
Use the conditionset to create a condition widget and add it into a display layout
Change the time conductor bounds and make sure there are no console errors
Go to a plan and change the time conductor bounds again. Ensure there are no console errors.
Go back to the display layout and change the time conductor bounds again. No console errors? Great!
Reproduce
Notes
The text was updated successfully, but these errors were encountered: