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

Windows 10 : running examples : closing druid main window doesn't stop cargo.exe #265

Closed
LeonGGX opened this issue Nov 6, 2019 · 2 comments · Fixed by #763
Closed

Windows 10 : running examples : closing druid main window doesn't stop cargo.exe #265

LeonGGX opened this issue Nov 6, 2019 · 2 comments · Fixed by #763
Labels
bug does not behave the way it is supposed to shell/win concerns the Windows backend

Comments

@LeonGGX
Copy link

LeonGGX commented Nov 6, 2019

Thank you for the great job you are doing in the field of Rust GUI ...

When running the examples on Windows 10, closing the main window doesn't stop cargo.exe from running. The window get closed, but the process in the back doesn't stop. You have to go to the console and use Ctrl + c to stop the process. Then you receive the following message :
error: process didn't exit successfully: D:\...\target\debug\examples\multiwin.exe (exit code: 0xc000013a, STATUS_CONTROL_C_EXIT)
Thanks for advice.

rust version : 1.38.0

@zaynetro
Copy link
Collaborator

zaynetro commented Nov 6, 2019

I can confirm that the same happens on macOS Mojave (10.14.6).

@cmyr cmyr added bug does not behave the way it is supposed to shell/win concerns the Windows backend labels Nov 6, 2019
@cmyr
Copy link
Member

cmyr commented Nov 6, 2019

Yea, thanks for this. It's a slightly tricky one because there are platform-specific expectations; on windows we should kill the application when the main window closes, but on mac we shouldn't.

There's a separate problem on mac where once the last window is closed the menu stops working. :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug does not behave the way it is supposed to shell/win concerns the Windows backend
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants