Introduce RESET keyword for schedule.wpi #30
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The code inside schedule script should not take care of the schudle clearing - it overwrites old schedule anyway. Empty schedule script file can be considered an explicit order to clear old schedule. 54609f1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As described here in the UUGear forum, I update the schedule.wpi file externally and set the new schedules by running
runScript.sh.In the moment one wants to unset the schedule, it doesn't work to just delete the schedule.wpi file as previously scheduled startup/shutdown don't get reset.
My proposal is to introduce a
RESETkeyword for the schedule.wpi file.