Bug Description
There seems to a difference between the Winit and Qt back ends. In the attached program bug-demo.zip
, we have:
- An
on_close_requested handler that always returns CloseRequestResponse::KeepWindowShown
- A button that causes
quit_event_loop() to be invoked
When running with the Winit back end (cargo run -- --backend winit), the "Quit" button exits the program as expected. But with the Qt back end (cargo run -- --backend qt), the "Quit" button seems to be ignored. It seems like returning CloseRequestResponse::KeepWindowShown causes the quit to be aborted.
Reproducible Code (if applicable)
Environment Details
- Slint Version: 1.15.1
- Platform/OS: Windows
- Programming Language: Rust
- Backend/Renderer: Qt
Product Impact
No response
Bug Description
There seems to a difference between the Winit and Qt back ends. In the attached program bug-demo.zip
, we have:
on_close_requestedhandler that always returnsCloseRequestResponse::KeepWindowShownquit_event_loop()to be invokedWhen running with the Winit back end (
cargo run -- --backend winit), the "Quit" button exits the program as expected. But with the Qt back end (cargo run -- --backend qt), the "Quit" button seems to be ignored. It seems like returningCloseRequestResponse::KeepWindowShowncauses the quit to be aborted.Reproducible Code (if applicable)
Environment Details
Product Impact
No response