-
Notifications
You must be signed in to change notification settings - Fork 6
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 a flag to auto-accept dialogs if triggered with --standalone-update-dialog #18
Comments
Sorry, didn't notice the |
it was not documented on purpose. It was used privately by the program to update AppImages with root access. But I guess you can use it if you want. It does not have the name fix in it though.(for now) |
Is it possible to add flags that will bypass the dialogs ? |
Yes we can. You can actually do that in the settings of the main Application but the standalone dialog box does not respect that so we would definitely need a flag from the command line. I'm busy right now, So this is gonna take some time. |
No rush. Thanks! |
I was about to ask for the exact same thing. Would be greatly appreciated! 👍
In both modes, there should no desktop notifications and no status bar plugin/widget, and AppImageUpdater should quit after the updating is done. Thank you. |
Okay the latest build has the following options,
Is this okay with y'all?
By default it does the above mentioned. I think you did not close the previous applications properly(Clicking on the 'X' in the title bar will not close it, you have to click on the exit button in the application). In the past the application did not implement the context menu for the tray icon so I think you were not able to close it, but now its been implemented, you should force kill any previous version that are running in the background and try the new one. |
Thanks for implementing. Graet work 👍 Question: Which of these can/cannot be used together?
From experimenting, the combination
Maybe it could be clarified in the help text. Thank you very much for this. |
I understood |
Yes it was my mistake, edited above. |
Maybe there should also be a way to suppress this dialog:
|
can there be an |
Actually I think the output should only be shown on the command line if requested with |
@probonopd Then how can you know if a update is completed successfully, Do you want a command line tool? If so why can't you use a command line tool like the official one?
You can use all the things together. When using When using
@luzpaz Yep. I think so too. I will add a verbose mode and hide all logs by default as suggested. If you want a CLI tool then I can make a separate one for that which is much better at displaying information CLI friendly. Do you want a command line tool? |
a CLI tool would be awesome, yes |
Personally I was not looking for a command line tool, I am trying to integrate the updater with an experimental version of appimaged that I am re-writing from scratch in Go (Golang). It can update AppImages by right-clicking on them, and I want to invoke AppImageUpdater. But now I can do that, so it's fine. |
I am using In other cases it does show the dialog: Actually it shows more than one dialog for just one AppImage: If the AppImage is already the newest version, then an information is shown. |
Try the latest version, it should be fixed. No we have new usage options,
Now the 'checking for update dialog' will not be shown unless you explicitly mention the So Use,
@probonopd is this okay? |
Perfect 👍 |
It would be nice to have the ability to invoke AppImageUpdater from the CLI and pass the AppImage that you want it to update.
Usecase:
$ ./AppImageUpdater.AppImage FreeCAD_0.19-18614.AppImage
Bonus: add a flag that automatically quits AppImageUpdater after it successfully completes its task.
The text was updated successfully, but these errors were encountered: