feat: expose freeze options as cli-args #3
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hello, I love the idea behind this project and I'm looking to use this for my own desktop's lockscreen.
I've been toying around with porting shaders available on https://www.shadertoy.com/ for use in the available lockscreen rotation but many of them need a freeze-timeout of longer than 10 seconds to complete their full animation cycle so I'm hoping to expose the options to configure it from the cli.
Please consider merging to allow for more flexible customization options. I've tried to keep the changes as minimal as possible and keeping them inline with how the rest of the project is designed. Hope to hear from you soon :)
NOTE: I was forced to remove Cargo.lock in order to compile the project on the most recent version of rust due to some issue with
proc_macro2. I assume others wanting to make use of the project may come across the same issue so it's been included in this PR.