-
Notifications
You must be signed in to change notification settings - Fork 15
Implement self-updater on application start #40
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
Conversation
9a454bb
to
fffe74c
Compare
5d5a6b8
to
c573ae1
Compare
With the added commits the self-updater is feature complete.
I also laid a framework for a future project to add a ui options menu where the end user can choose whether to stretch the window to fill their display or stick with the 4:3 aspect ratio as well as choose the ui button colors and letters since several retro handhelds have varying button layouts (Xbox vs Nintendo layout, different physical button colors etc.) |
a97243f
to
6b89bbc
Compare
Since we use execv (same process) and argv (same arguments) without user input, this is generally safe and could be ignored. On the other hand, it could also be changed to relaunch the shell script, but this requires knowing where the shell script exists. For now ignore the warning.
Description
__version__.py
browser_download_url
It doesn't look quite the same as when downloading a rom, and since it occurs before anything else renders, I wonder if I'm missing some steps in the render pipeline that could otherwise make it look better. It does successfully download the latest
.muxapp
release if__version__.py
is not present.