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

Bad UX #48

Open
marcinn opened this issue Apr 9, 2020 · 2 comments
Open

Bad UX #48

marcinn opened this issue Apr 9, 2020 · 2 comments

Comments

@marcinn
Copy link

marcinn commented Apr 9, 2020

Hi.

I'm enabling equalizer, setting up knobs, saving as new preset. Then I'm trying to tune up settings. As a result the preset name is clearing out and I cannot save the preset.

When I want to type a name of the preset (to save using same name), the application loads previously saved state during typing and destroys my last tunings.

So I cannot modify my preset.

@travnick
Copy link

travnick commented Dec 9, 2022

True. I found it very annoying.
Workaround is to name it with my_preset_1, my_preset_2, so it does not override my new settings while typing the new name.

@ghost
Copy link

ghost commented Dec 9, 2022

That happens because the name field is automatically acting as a search field. I'm not sure if that is something that can be disabled through some flags or a different logic has to be implemented in the code. Stumbled into this issue myself but didn't dig deep enough to find a possible fix. Maybe at some point...

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

2 participants