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

[BUG] : random speed is always true in 0.1.0 - fixed in 0.1.1 #13

Closed
SkwalExe opened this issue Mar 30, 2022 · 1 comment · Fixed by #12
Closed

[BUG] : random speed is always true in 0.1.0 - fixed in 0.1.1 #13

SkwalExe opened this issue Mar 30, 2022 · 1 comment · Fixed by #12
Assignees
Labels
bug Something isn't working

Comments

@SkwalExe
Copy link
Owner

SkwalExe commented Mar 30, 2022

Hey, just found out there is a bug with the --random-speed option, this options sets random_speed to true but it is true by default so it is never false

...
let mut args: Vec<String> = std::env::args().collect(); // arguments vector
let mut speed = 70; // the delay in milliseconds between each chars
let mut random_speed = true; // if the speed is random between 20 and speed
args.remove(0); // remove the program name
...
"--random-speed" | "-r" => {
                random_speed = true;
                args.remove(0);
}

If you have this problem just update to 0.1.1

@SkwalExe SkwalExe added the bug Something isn't working label Mar 30, 2022
@SkwalExe SkwalExe self-assigned this Mar 30, 2022
@SkwalExe SkwalExe linked a pull request Mar 30, 2022 that will close this issue
@SkwalExe SkwalExe pinned this issue Mar 30, 2022
@github-actions
Copy link

Hi @SkwalExe Thanks for opening this issue 🎉 You should receive a response soon.

@SkwalExe SkwalExe changed the title BUG : random speed is always true in 0.1.0 - fixed in 0.1.1 [BUG] : random speed is always true in 0.1.0 - fixed in 0.1.1 Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant