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

Improve search field #760

Closed
Sti2nd opened this issue May 22, 2014 · 11 comments
Closed

Improve search field #760

Sti2nd opened this issue May 22, 2014 · 11 comments
Milestone

Comments

@Sti2nd
Copy link
Contributor

Sti2nd commented May 22, 2014

WOW. LMMS got a search field at the bottom of the tree view in the Sidebar? I finally found out... It kinda sucks though, it only search for visible text, not files in folders.

So nr.1 wanted improvement is the ability to search inside folders and subfolders.

And then we have loosely discussed a search function here #614 Which summed up also adds tags as a possibility to list samples and presets.

Edited 2014-11-10 @tresf, added screenshot
image

@musikBear
Copy link

in think it search every -opend- folder, but sadly not subfolders, in an opend folder, but the context-search is absolutely super! If you just found that rigt now, then observe that you have token search!!!
For instance, If you have an instrument named
shortSuperSawNr3
The search will find that if you search for any of sup, saw, nr3, you do -not- have to remember like first 3 letters. Thats wonderfull. I use it to set families of instruments : _sa will display any and all saws (if the folders are opend, that is :)

@eagles051387
Copy link

This shouldnt be too hard to fix. If what you are saying is accurate what
its doing is a non recursive search and not searching through folders which
are not open.

On Fri, May 23, 2014 at 1:21 PM, musikBear notifications@github.com wrote:

in think it search every -opend- folder, but sadly not subfolders, in an
opend folder, but the context-search is absolutely super! If you just
found that rigt now, then observe that you have token search!!!
For instance, If you have an instrument named
shortSuperSawNr3
The search will find that if you search for any of sup, saw, nr3, you do
-not- have to remember like first 3 letters. Thats wonderfull. I use it to
set families of instruments : _sa will display any and all saws (if the
folders are opend, that is :)


Reply to this email directly or view it on GitHubhttps://github.com//issues/760#issuecomment-43996771
.

Jonathan Aquilina

@tresf tresf added this to the 1.2.0 milestone Nov 10, 2014
@lukas-w
Copy link
Member

lukas-w commented Nov 24, 2014

@eagles051387
While a recursive search would not be hard to implement – please do! – it may be slow. We should consider indexing the file trees.

@Sti2nd
Copy link
Contributor Author

Sti2nd commented Dec 21, 2014

Huh, 1.0.100 search the folders too. Don't know who implemented this, thanks. Close?

@lukas-w
Copy link
Member

lukas-w commented Dec 21, 2014

@Sti2nd It doesn't for me. It only searches in folders I already opened.

@Sti2nd
Copy link
Contributor Author

Sti2nd commented Dec 21, 2014

Oh, they were stored in memory somewhere. Had opened all the preset folders and searched for sweep, then closed them all and searched for sweep again, and it filtered out all the other presets and folders except the two with sweeps presets in them.

@badosu
Copy link
Contributor

badosu commented Jan 27, 2015

@curlymorphic Did your latest patches in this area address this issue? Or is there still something to be improved?

@tresf
Copy link
Member

tresf commented Jan 28, 2015

It works and works well, but it doesn't auto-expand search results. Closing since that's really what is being requested. We can allow users to open another one to do tree expansion.

@tresf tresf closed this as completed Jan 28, 2015
@badosu
Copy link
Contributor

badosu commented Jan 28, 2015

I don't understand, @tresf, if @curlymorphic changes did not solve this issue, why close it?

@tresf
Copy link
Member

tresf commented Jan 28, 2015

@badosu they did. The nice-to-have is to auto-expand the search results, which was never part of this request.

@badosu
Copy link
Contributor

badosu commented Jan 28, 2015

@tresf Oh, fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants