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
Why does Fyne close application if no Windows are shown? #1080
Comments
In most desktop operating systems closing the last window closes the app. |
Can I hide the main window instead of closing it? |
There is an ongoing discussion in this area - but unless the user can tell the difference I’m not sure that it seems like a good idea. What is the difference between closed and hidden for a user, how can they bring them back? As I said before the more we can know about your platform and why this is important the more it can inform the discussion. |
I am going to close this as a duplicate of #467 - if you intercept the close and call Hide() instead the behaviour you desire will be possible. |
I leave this to document a use case: TLDR: My app show/hide flow is through a trayicon. Use case:The app manages a dev environment where:
Once launched the application, the app shows a try icon. On press of the tray icon, it shows the fyne window. Upon close, the trayicon is show again. The app flows as this:
Then the app exists... and don't know how to restart the UI within the same process. |
the call to *) Use |
@andydotxyz I have the same query as @ababo
|
That is expected. As listed above you can use |
Okay, It means fyne doesn't support new a window in hidden status,but can be hidden by the user's click. Thanks a lot. |
I don’t understand why you think this means a window can’t be created hidden? This is absolutely possible - just don’t call |
I'm not express clear, I want a master window created in hidden default, other windows can be closed.
|
That code has forgotten to call |
I would like to have an app event loop running while I open and close windows without exiting with a last window? What's behind this design decision and how can I overpass this behaviour? Thanks in advance.
The text was updated successfully, but these errors were encountered: