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: sizeBox should not allow null input #184

Open
dvxry opened this issue Dec 8, 2023 · 1 comment · May be fixed by #185
Open

Bug: sizeBox should not allow null input #184

dvxry opened this issue Dec 8, 2023 · 1 comment · May be fixed by #185
Assignees

Comments

@dvxry
Copy link

dvxry commented Dec 8, 2023

Description

Every time I try to run the visualizer and I am trying to reduce the number of bars, I struggle to notice exactly where my cursor is since it doesn't show up. I often end up just removing all the bars and I end up running the program with nothing in the sizeBox which causes it to promptly crash

Not sure if this counts as a bug but it would be nice to implement a cursor for users to see where they're typing in the textbox and also to control input to a certain number of bars

Potential solution

I don't think it should be too difficult but I suspect doing something as simple as raising an error when a user tries to hit play with no value inside the bar

If anyone could implement this that'd be great!

@aaravtanti
Copy link

Hey, I can work on this issue!

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

Successfully merging a pull request may close this issue.

2 participants