-
Notifications
You must be signed in to change notification settings - Fork 163
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
Add UI to the updater process #39
Comments
We might be able to remove the need for the external Updater entirely - would be a better solution |
Agreed
|
Any updates on this? |
I'm afraid I don't have enough time to work on this at the moment, PRs welcome |
We are facing a similar issue and I propose the following solution: Instead of adding UI, we can add callbacks to which the calling application should hook and display UI. This works perfectly during the checking, preparing and applying phases. The calling application is shut down only during cold update, which is typically a small part of the overall update process. Can submit a pull request if the idea seems OK. |
The problem is running updater takes a couple of seconds in my case.
During that time the main application is inaccessible, but since it's taking a while the users might want to relaunch it, thinking something has failed, and that it should have re-launched by now.
Having some sort of (other than the console) UI (A progress bar + some text saying "update in progress") would help.
The text was updated successfully, but these errors were encountered: