-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
No longer able to reorder stacked plots #6158
Comments
Reordering does happen when navigating away and navigating back but should happen immediately |
Was able to replicate the issue, and @ozyx's workaround: Screen.Recording.2023-01-25.at.11.19.21.AM.movNow looking into what's going on. |
Testathon 2/6/23 The reorder now only happens upon saving the Stacked Plot. We don't have to navigate, but does not update in real-time in edit mode. |
Testathon 2-6-2023: Seeing the same thing as @rukmini-bose above. Reorder happens but only after save |
Testing Instructions
|
…l time (#6346) * fix: ensure Vue can react to stacked plot item reorders - Use Vue.$set instead of assignment so Vue can pick up StackedPlot composition reorders immediately * test(e2e): add test for stacked plot item reorder * docs: specify plot item order in comments * fix: correct page.goto() url
… real time (nasa#6346) * fix: ensure Vue can react to stacked plot item reorders - Use Vue.$set instead of assignment so Vue can pick up StackedPlot composition reorders immediately * test(e2e): add test for stacked plot item reorder * docs: specify plot item order in comments * fix: correct page.goto() url
verified testathon 3/9/23 |
Verified fixed! |
Summary
Historically it has been possible to reorder the sub-plots within a stacked plot by changing the order of the elements in the element pool. The reorder function was added to the composition API to facilitate this.
Expected vs Current Behavior
The order of plots within a stacked plot should be the same as the order of composition in the elements pool
Steps to Reproduce
Environment
Impact Check List
Additional Information
The text was updated successfully, but these errors were encountered: