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

Fever States #3

Open
RubenSandwich opened this issue May 19, 2019 · 0 comments
Open

Fever States #3

RubenSandwich opened this issue May 19, 2019 · 0 comments

Comments

@RubenSandwich
Copy link
Owner

By "fever" states I mean when the volume rises up to max and stays there consistently. When you detect the end of a "fever," i.e the coder slowed down (and maybe went over to the Explorer to make a file), add a buffer between the end of this "fever" and the start of the volume decreasing. This gives the coder some time to create a file in the Explorer, run a command, etc., without it seeming like they broke their flow. If the time buffer hits, then logic would state that the coder actually did break their flow.

Perhaps this could also be a setting, both whether the buffer's enabled and how long it is.

(Taken from the advice of: @alkalinethunder)

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

No branches or pull requests

1 participant