Skip to content
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

Auto update #58

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Auto update #58

wants to merge 3 commits into from

Conversation

LendaUrbana
Copy link

Inclusion of automatic updates

CTRL+SHIFT
+ R  - Start Record
+ S  - Stop Record
+ P -  Record
+ UP ARROW - Start Replay / Resume Replay
+ DOWN ARROW - Stop Replay
+ RIGHT ARROW - Forward Replay
+ LEFT ARROW - Forward Replay
+ END - Stop Replay
@nguyenquyhy
Copy link
Owner

Thanks very much for the PR. I'll work on merging this into the tool.

Things that I am still thinking about on this topic:

  • Release schedule: normally I don't want auto-update to trigger right at release to avoid huge impact should I release any bugs 😅. Would also be nice if there is a way to stop auto-updating without deleting the whole GitHub release.
  • Single file deployment Single .exe #59: at the moment I am working on deploying this whole recorder as a single .exe file for a click and run experience (not installer). This might be at odd with autoupdater.
  • Opt-out: I don't really need a way to opt-out of update checking completely, but would be nice if the tool can remember the last "No" answer and show an unobstrusive message instead of a prompt on next launch.

@LendaUrbana
Copy link
Author

As for the situation of remembering the last answer in case of up to date, a check can be included in the expanded screen with the option, I don't know which is the feasibility of recording a json file with the user's local settings. For example the parameter of not updating. And even to store other parameters in the future. For example, in case of automatic save, the default folder can be stored. It is an idea of how it can be done.

@LendaUrbana
Copy link
Author

I had an idea not to release automatically, once published in git, I don't know if it is possible to change ul assert in realease, but it is possible to include a file with a parameter. This file can be read, if the status is ok for release it starts the update process. In the octokit there may also be some parameter that is possible to carry out this control.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants