The search bar still is not resizable and the toolbars in general are still not lockable (outside of party mode, which is not ideal).

Thanks for your suggestions. Alpha 6 has incorporated most of your ideas.

Thx.

-Rusty

When I use search, 9 times out of 10 I'd want it to search the entire library. Certainly introduce an option to limit it to the current view, but don't make that the default.

[quote="JoergR"]I'm voting for "Search entire library" because I don't want to navigate first and then drop a query.[/quote]

I would like to see "search in current node" as the default...
but the default node selected at startup should be the library node, and this should list all files (filtered if filtering is on).
This would mean a search immediately 'would' be searching the whole library even though it's set to search current node.

Also, remember that a global search is available by pressing ctrl-F at anytime... so if you have "search in current node" activated, you can still search globally... but if you have "search whole library" activated, you have to change the option first before you can search current node.

It would essentially be making "search in whole library" [i]easily[/i] accessible by two different methods and "Search in current node" not immediately accessible. - why not share the methods between them.

Either way.. it should persist, so ultimately, it doesn't matter that much except that it could cause new users to not realise whatever wasn't showing was possible.

Dale.

Dale.

I like Steegy's suggestion. Since such a search box is implemented in almost all browsers, everybody knows how to use them.

Another idea would be like Outlook 2007 does it. It has kind of a "header bar" above the main listview which shows in which node you're currently in (e.g. "Inbox", "Outbox", ...) and in this bar there is a small textbox which instantly filters (=searches as you type) the current view. In addition to that, there's the search toolbar (like MM has right now).

I'm leaning towards searching the entire library by default, since most of the time I'm looking for something I have little idea of (and using keywords) or trying to find all instances of a phrase / title / artist etc. As I have yet to try MM3 my style of use may change once I get used to the new system.

Still I imagine it would be very useful to have quick access to searching within current nodes, playlists and global search results.

I also vote for the ease of choice, no matter what is the default.
Firefox's way.

search the entire library.

because it might have been removed completely and you don't know that by looking in one node.

or it is not in the node you thought it was, and you won't find it by looking in only one node.

if you're searching for it then its painfully obvious that you have lost it and don't know where to look. 8)

I have a slight preference for "Search Entire Library". What I would really like to see would be a radio button next to the search box that would switch back and forth between "Search Entire Library" and "Search Node" and which would be persistent between sessions.

I'm voting for "Search entire library" because I don't want to navigate first and then drop a query.
BUT I would love to see the same functionality like I can use in MediaPlayer, Vista Search, Google, ... : controling the search with key words like "artist:<search phrase>" or "title:<search phrase>" or "ranking:".

User choice.

Selection visible and selectable in single search window as noted above.

So...no vote either way, I want both.

ohh...sorry i didn't give a reason.

I assume "Search selected node only" would mean just search down the tree from the tree location your cursor currently has selected...I would find this cumbersome....in working with the library, I would most often have to manually move "up" the tree from where I currently was to the area I would assume needed to be searched...a lot of decision, distraction and moving back and forth to no purpose....

Size mainly would be the reason to use "Search selected node only" As Randall noted above, a complete search of a large library is very slow. MM maxes out my CPU here....yet MOST often a complete search IS what is wanted or needed. For example: I am experimenting with breaking my library up into smaller physical units/collections...the smaller range search might be useful here...

Ultimately...practically for most users and intuitively for all users, when we ask for a search we just want it done, and with complete results...no thinking please...so a full search seems the only logical "default" if a choice actually has to be made.

My preferred default option is to limit within the current filter criteria. My library is quite large (110K) and a search of the entire library can take quite a long time and is difficult to stop once started.

However, I agree that this should be user selectable.

Yes, I use this type of search box in Firefox and it's so useful cos you can see what mode you're in straight away! :)

[quote="Steegy"]
To put it simple, I'd like a search box similar to that of web browsers like Maxthon:
[img]http://img515.imageshack.us/img515/9247/search20070712221141wx2.png[/img]
With one look, you could see what MediaMonkey is searching on (all fields, title, artist, lyrics, ...) by an icon and the faded text in the search box. By clicking the icon, the user could select a different search field from a list (like shown [url=http://img412.imageshack.us/img412/7636/search20070712221305ml3.png]here[/url]).
The search glass icon at the right activates the search, just as pressing the Enter key does (the search would not start during typing). An extra button on the right (or some other solution) would make it clear that there's also an advanced search possible.
The search box itself would have a drop down list with the past searches, and an item to clear the search history.
[/quote]

I agree w/Steegy, with the lone exception that I see no need for a second search box. Actually, I'm very happy with the way MM3A5 handles searches right now, giving us a choice as to entire library or current node search, but Steegy's idea would display the active search - i.e., either library or current node - in the search box.

Less importantly, I agree that a library-wide search should be the default, agreeing with the others that the choice to use either is more important.

Thanks, Danny

[quote="Steegy"]As long as the user can choose and this choice is persisting on restart of MM, I can live with both situations as default.

To put it simple, I'd like a search box similar to that of web browsers like Maxthon:
[img]http://img515.imageshack.us/img515/9247/search20070712221141wx2.png[/img][/quote]


I agree with Steegy, far more important than what the default is, is how it is displayed to the user which mode it is in, and that it retains (persists) that selection across restarts.