-
Notifications
You must be signed in to change notification settings - Fork 4
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
large graph viz: cliping #38
Comments
David:
This would require catching the resize event and appropriately changing
the viewport based on the new window dimensions. This means that the
window to viewport transform should then use the new dimensions. We can
wait till the end and if we have time, we can consider it.
-- krs
On 2/23/19 7:22 PM, Erik Saule wrote:
It seems that on he large graph visualization if you rescale the
"frame" where the visualization is, the cliping field of webgl does
not update correctly.
It is not urgent.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#38>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFZSOE6u8Ks9SYwXkpuVUzq_QKFhuNBzks5vQds5gaJpZM4bOPf_>.
--
Kalpathi Subramanian Ph: 704 687 8579
Associate Professor Email: krs@uncc.edu
Dept of Computer Science Web:http://webpages.uncc.edu/krs
The University of North Carolina
Charlotte, NC 28223-0001
|
So it turns out that is not a webgl problem. The main problem is that the html 5 specification does not allow to wait on a resize event even if the css enables the resize icon to be there. The resize event exist but is only triggered by window resize and not in page resize. There will be a proper javascript event that will be integrated eventually. Pretty annoying in the mean time. |
in 2019 I commented that there was a missing JS event. Is it a thing now? |
It seems that on he large graph visualization if you rescale the "frame" where the visualization is, the cliping field of webgl does not update correctly.
It is not urgent.
The text was updated successfully, but these errors were encountered: