-
Notifications
You must be signed in to change notification settings - Fork 50
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
Should wob really exit due to invalid input? #22
Comments
I would also rethink behaviour for inputs out of range [0;100]. It is not something unimaginable that I want to set my volume to 150%... Ultimate solution would be displaying the bar as if it were set to 100% with the text in the middle Of course all of these would be set via flags so I'm proposing:
Temporary solution
|
You can set maximum value via One thing I want to add is to print input that caused wob to exit. With startup command like this, it should give you some hints about what went wrong.
|
My solution is this: |
Implemented in #67 |
I don't have a strong opinion on this but I was wondering if it wouldn't be better to just ignore invalid input (and print a warning to
stderr
or show some graphical indication of a failure, e.g. a red overlay bar or error message).An advantage of the current behaviour (exiting) is that errors in scripts etc. become more apparent, but it might also be annoying when testing scripts as one would possibly need to restart wob quite often. Or if users aren't aware of this behaviour and don't see the output (e.g. when started via sway's
exec
) they might think that it did crash for another reason.If there where some graphical indication that invalid input was received this might be better / more comfortable. Or one could introduce a flag to let the user choose the behaviour.
The text was updated successfully, but these errors were encountered: