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
Hey there,
My overall goal with my application is to be able to have an icon on the taskbar that can change depending on status, that also allows you to click on the icon to open the GUI, then upon closing the GUI (depending on user preference) either hide the window back to just a taskbar icon or quit the whole application. I am trying to figure out where to actually start in implementing this and if NativeShell is capable of doing/allowing this, or if it is going to end up being more of a limiting factor.
I see that, at least on the user implementation side of things, the window_manager.createwindow and run_loop seem like they could be delayed and be called at a later time, as opposed to right away at application launch (though, I have not actually tested this yet), but is there any way to destroy the window in a manner in which it could be called again to recreate it without there being issues, or once it is created, that is basically it and it ends up being "all or nothing"?
If you happen to have any insight into this, whether you think it might be possible or not, I would greatly appreciate it.
Thanks,
-MH
The text was updated successfully, but these errors were encountered:
Hey there,
My overall goal with my application is to be able to have an icon on the taskbar that can change depending on status, that also allows you to click on the icon to open the GUI, then upon closing the GUI (depending on user preference) either hide the window back to just a taskbar icon or quit the whole application. I am trying to figure out where to actually start in implementing this and if NativeShell is capable of doing/allowing this, or if it is going to end up being more of a limiting factor.
I see that, at least on the user implementation side of things, the window_manager.createwindow and run_loop seem like they could be delayed and be called at a later time, as opposed to right away at application launch (though, I have not actually tested this yet), but is there any way to destroy the window in a manner in which it could be called again to recreate it without there being issues, or once it is created, that is basically it and it ends up being "all or nothing"?
If you happen to have any insight into this, whether you think it might be possible or not, I would greatly appreciate it.
Thanks,
-MH
The text was updated successfully, but these errors were encountered: