constellation
constellation copied to clipboard
Opening a view with a few graphs open will cause lag and resizes
Prerequisites
- [ ] Put an X between the brackets on this line if you have done all of the following:
- Running the latest version of Constellation
- Attached the Support Package via
Help
>Support Package
- Checked the FAQs: https://github.com/constellation-app/constellation/wiki/FAQ
- Checked that your issue isn't already filed: https://github.com/constellation-app/constellation/issues
- Checked that there is not already a module that provides the described functionality: https://github.com/constellation-app/constellation/wiki/Catalogue-of-Repositories
Description
If you open a view when you have a few graphs opened (ie. 8 graphs) it will display an odd visual bug as well as a slight amount of lag. The more graphs opened, the worse the problem is.
Also occurred in previous beta releases
Steps to Reproduce
- open 8 new graphs
- open histogram view - Any view will do 2a. visual bug occurs
- close histogram view 3a. visual bug occurs
Expected behaviour: fast switching with no visual bug
Actual behaviour: visual bug and lag when opening
Reproduces how often: 100%
Additional Information
The more graphs opened, the more it lags.
@aldebaran30701 and I were discussing this and we believe that what's happening is each individual graph is being resized when a view is open, which would be why it lags more depending on how many graphs you have open. A potential solution could be to only resize the active graph and then resize the other graphs individually later on as necessary.
The flicker with a single graph is also noticeable and good if we can fix.
(Slow motion:)
This issue is stale because it has been open for 6 months with no activity. Consider reviewing and taking an action on this issue.
Confirmed this is still happening with version 2.3.
This issue is stale because it has been open for 6 months with no activity. Consider reviewing and taking an action on this issue.
This issue is stale because it has been open for 6 months with no activity. Consider reviewing and taking an action on this issue.
This issue is stale because it has been open for 6 months with no activity. Consider reviewing and taking an action on this issue.
This issue is stale because it has been open for 6 months with no activity. Consider reviewing and taking an action on this issue.
This seems to have resolved itself now and is no longer happening with R2.10 (latest nightly build). I will close this issue off seeing it can't be replicated any more.