Skip to content
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

Resizing or moving a window pauses a bevy app #17529

Closed
aloucks opened this issue Jan 24, 2025 · 1 comment
Closed

Resizing or moving a window pauses a bevy app #17529

aloucks opened this issue Jan 24, 2025 · 1 comment
Labels
C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled

Comments

@aloucks
Copy link
Contributor

aloucks commented Jan 24, 2025

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

cargo run --example animated_material

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.

@aloucks aloucks added C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled labels Jan 24, 2025
@mockersf
Copy link
Member

Duplicate of #17488

@mockersf mockersf marked this as a duplicate of #17488 Jan 25, 2025
@mockersf mockersf closed this as not planned Won't fix, can't repro, duplicate, stale Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled
Projects
None yet
Development

No branches or pull requests

2 participants