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
I am observing two issues here. The first is the presence of duplicates entries in the time conductor history, which should not appear. The second is that clicking on an historical entry in real-time mode does nothing, the conductor remains in real-time mode with the same offsets.
Expected vs Current Behavior
Expected behavior needs clarification with @charlesh88
Steps to Reproduce
Load Open MCT
In the Time Conductor, switch to real-time mode
Click the history button to expand the popup
Note that the popup contains duplicate entries
Click on history entries
Observe that nothing happens in the time conductor
Environment
Open MCT Version: 2.0.7
Deployment Type: Dev
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?
The text was updated successfully, but these errors were encountered:
Yeah, there's a lot going on here. There should only be offsets in realtime mode history menu. When click on that it should set those offsets and keep you in realtime mode. Same deal for fixed time, only fixed time bounds should be present in the history menu and they should set the bounds for fixed time mode.
Summary
I am observing two issues here. The first is the presence of duplicates entries in the time conductor history, which should not appear. The second is that clicking on an historical entry in real-time mode does nothing, the conductor remains in real-time mode with the same offsets.
Expected vs Current Behavior
Expected behavior needs clarification with @charlesh88
Steps to Reproduce
Environment
Impact Check List
The text was updated successfully, but these errors were encountered: