-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
ignore capitals in Token-search #4925
Comments
Currently, it looks like this(case-sensitive):
The suggestion is(case insensitive):
I think it should be easy to change the behavior because There are several different options:
Please let me know user opinion! |
yes, an option for user to decide, is a brilliant idea! |
:| cant 'vote' -The smileys are not click-able in this browser, so you can add one for "3"
|
@musikBear I'll add a vote for you for ❤️. For the record though, my vote is 👀 :) |
@SecondFlight Thanks! :+1 |
Definitely change it. When you have a ton of presets, it ends up looking like its been alphabetized twice (first all the caps, then the lowercase), which makes finding the preset/sample you want harder than it needs to be. |
hey all I'm fairly new to LMMS coding, but I'd I think I can start on this one. |
OK. Assigning you to the issue. ;) |
Thanks, just to make sure we're on the same spot we're talking about list elements like the my presets browser i.e. in the fixed version orion.xpf should be put before SString.xpf see example screenshot from a freshly built lmms: correct? So concludingly:
should be adjusted. Do we care also about the LADSPA Plugin Browser? Anything else I missed? |
That item is an odd one. It let you look at options, but non can be changed. I have to say that besides giving LADSPA-devs an option to look into existing settings, its hard to see why we still have this component as a std-component in lmms(?) Imo we could have it as a external separate downloadable module. |
alright I think my solution is ready, however I have no push-permissions:
Can someone please set me up? |
We use Pull Requests. You'll want to fork LMMS, push your changes to a branch on the fork, and then create a PR via the Github web interface. |
Sometimes i find it difficult to find a resource, even though i can remember its name. The reason is that LMMS make distinktion between capital letters and small letters.
So where it would be logical that 'Horn01' and 'horn02' was listet directly after each other, they wont be if we have a series of 'Hot xyz' named resources.
I suggest that capitals in names/ labels are ignored in Token-search-listings.
(May bee an accessibility related thing as well)
The text was updated successfully, but these errors were encountered: