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
While testing the WGPU render backend and Winit platform crates I created, I get following odd error:
Some elments keep expanding once they are visible. In the screenshot you can see that the drawing area of the painting widget expands and keeps expanding. If you scroll down until the end of the drawing area is visible, the expanding will stop.
Anothe example:
Do you maybe know where I could start debugging this? I have a hard time figuring out how the backend or the windowing integration could cause this behavior.
The code for reproducing this problem can be found here can be found in this example project.
The text was updated successfully, but these errors were encountered:
I've had those bugs before, but fixed them, so weird seeing them pop up again! Interestingly, when I run your code it all works as expected.
What is the pixels_per_point (window.scale_factor()) on your system when you run your example? Maybe Egui has a rounding error for when pixels_per_point is non-integral.
I run my desktop in 4k with 150% scale. So pixels_per_point is 1.5.
I can reproduce the same error with the glium backend, but it only triggers when I move the mouse, since the application doesn't run unlimited (ControlFlow::Poll) and waits for events (ControlFlow::Wait).
Hi,
While testing the WGPU render backend and Winit platform crates I created, I get following odd error:
Some elments keep expanding once they are visible. In the screenshot you can see that the drawing area of the painting widget expands and keeps expanding. If you scroll down until the end of the drawing area is visible, the expanding will stop.
Anothe example:

Do you maybe know where I could start debugging this? I have a hard time figuring out how the backend or the windowing integration could cause this behavior.
The code for reproducing this problem can be found here can be found in this example project.
The text was updated successfully, but these errors were encountered: