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
I am not crazy! I will not fill out this form just to ask a question or request a feature. Pinky promise.
Is there an existing issue for this?
I have searched the existing issues.
Is this issue related to iced?
My hardware is compatible and my graphics drivers are up-to-date.
What happened?
If you have a layer that is not drawn either because it is fully outside of the application window, or because its snapped bounds have an area of zero, this breaks subsequent layer draws. This is because at
Is your issue REALLY a bug?
Is there an existing issue for this?
Is this issue related to iced?
What happened?
If you have a layer that is not drawn either because it is fully outside of the application window, or because its snapped bounds have an area of zero, this breaks subsequent layer draws. This is because at
iced/wgpu/src/lib.rs
Lines 271 to 275 in f2c9b6b
iced/wgpu/src/lib.rs
Lines 277 to 279 in f2c9b6b
quad_layer
,mesh_layer
andtext_layer
indices.Here is a video of this occuring in a real iced app:
2024-12-18.12-19-02.mp4
and the relevant lines in the source code of this app: https://github.com/generic-daw/generic-daw/blob/b5593615b46625cfde0f194d16582f15cc672d7a/src/generic_front/widget/track.rs#L56-L59
What is the expected behavior?
Layer rendering doesn't break when a layer is not visible.
Version
crates.io release
Operating System
Linux
Do you have any log output?
No response
The text was updated successfully, but these errors were encountered: