Timeline summary window box can shrink unexpectedly
See original GitHub issuePrerequisites
- 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/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/repositories-catalog
Description
Dragging the Timeline’s summary window box toward the right edge of the summary window will cause it to jump around and in the process slowly shrink.
Steps to Reproduce
- Create a sphere graph
- Open the timeline view, making sure the summary window is visible
- Drag the box in the summary window to the right edge
- Keep trying to drag the box across and notice the timeline jump around and the box slowly shrink
Expected behaviour: Summary window box is not affected by forcing box beyond current summary window bounds Actual behaviour: Summary window box shrinks when trying to go past summary window bounds
Reproduces how often: 100%
Additional Information
The main effect of this bug is that it acts as an unexpected zoom in
Issue Analytics
- State:
- Created 4 years ago
- Comments:7
Top Results From Across the Web
Randomly shrinking timeline window - Avid Community
Since about MC 5.0 I've noticed my timeline window will randomly make itself extremely small and relocate to the upperleft corner of my ......
Read more >Pages randomly appear completely "blank/white" until I resize ...
When I clicked new issue the page just turned white until I resized the chrome window. What is the expected behavior? ... What...
Read more >Optimize Cumulative Layout Shift - web.dev
Cumulative Layout Shift (CLS) is a metric that quantifies how often users experience sudden shifts in page content.
Read more >Arrange the Final Cut Pro main window - Apple Support
The main areas of the Final Cut Pro window include the browser, viewer, timeline, sidebar, and inspector. You can show, hide, and resize...
Read more >Create timeline animations in Adobe Photoshop
Learn how to create timeline animations in Adobe Photoshop. ... You can also preview the animation in the Save For Web dialog box....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I finally worked it out, going one step up the function chain from
performDrag()
you get the following function:The issue here ends up being the final line which assumes that there has been movement when actually movement only occurs if it meets the boolean conditions within the functions. Since
origin
was used to help determine how far we have moved, this incorrect assumption from the last line of the above function is what is causing the problem.Moving this line to within the if conditions of the functions it calls seems to fix the issue
performDrag()
inOverviewPanel
is where it is determined whether or not dragging the summary box should be done. Whether it is done or not is determined by the following if condition in the function:I don’t think there is an issue with the if condition as this is used elsewhere and makes sense. What I have discovered during debugging though is that
histogram.getWidth()
may be changing value unexpectedly. This function will run multiple times depending on the size of the drag but every time the if condition evaluates to true this results in the histogram width changing somehow and I’m unsure as to why or how. Someone with more knowledge in this may be able to explain more as to what is actually being measured for the histogram width but my understanding is that it shouldn’t be changed by this.