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
Clicking any area of the border with the intention of moving or resizing the window pauses the render loop.
I was somewhat expecting that it might pause when the the top section of the border is clicked and dragged for moving the window, but was surprised that resizing also paused execution due to the way that winit is designed.
It would be nice if bevy provided a way to run the window event processing on a different thread from the render loop thread (on supported platforms) so that window movement and resizing would not cause the application to stop execution.
The text was updated successfully, but these errors were encountered:
Bevy version
main branch
deb135c
Relevant system information
$ cargo --version -vvv
cargo 1.83.0 (5ffbef321 2024-10-29)
release: 1.83.0
commit-hash: 5ffbef3211a8c378857905775a15c5b32a174d3b
commit-date: 2024-10-29
host: x86_64-pc-windows-msvc
libgit2: 1.8.1 (sys:0.19.0 vendored)
libcurl: 8.9.0-DEV (sys:0.4.74+curl-8.9.0 vendored ssl:Schannel)
os: Windows 10.0.22631 (Windows 11 Professional) [64-bit]
What you did
What went wrong
Clicking any area of the border with the intention of moving or resizing the window pauses the render loop.
I was somewhat expecting that it might pause when the the top section of the border is clicked and dragged for moving the window, but was surprised that resizing also paused execution due to the way that winit is designed.
It would be nice if bevy provided a way to run the window event processing on a different thread from the render loop thread (on supported platforms) so that window movement and resizing would not cause the application to stop execution.
The text was updated successfully, but these errors were encountered: