[quote]Re. changing F7 behavior, I don't think that's necessary for now (just resolving the first issue fixes the most significant problems).[/quote]

It could be nice to change it tho IMO.

CMS:

This is fixed in 1203 you have to go to Tools -- Options -- Library -- Appearance to change the setting for it to work.

Nyn

Fantastic :D 1203 is going to have some much needed fixes for me.

Nyn

[quote="cmx"][b]make it user configurable[/b][/quote]


from mantis

[quote](0015669)
rusty (administrator)
2008-12-16 15:25
edited on: 2008-12-16 15:27

Seems configurability is needed for this feature (at least until DB performance improves further). I've modified the suggested wording to reflect the fact that all tracks aren't necessarily shown (depending on the active filter):

Tools > Options > Library > Appearance (first entry)
[x] Show tracks in the Library node

Hint: Enable to show tracks directly in the Library node. Disable for better performance in a huge library.

Re. changing F7 behavior, I don't think that's necessary for now (just resolving the first issue fixes the most significant problems).



(0015681)
petr (developer)
2008-12-16 17:38

Will be in 1203
[/quote]

[quote="Teknojnky"]Another potential option would be, to make F7 collapse the tree without changing the current node.[/quote]

A long standing request of mine :( (and remember the current selected track)

thx techno I will try the maintain/cleanup...there were some issues with my old DB and the beta version, hopefully things will shake out. (I was of course exaggerating the severity of the CPU drag...lol...but as I'm sure you see with your DB...there is WAY too much lag for practical ease of use if all tracks are continually being loaded in the main and with other things happening in MM like syncing and writing Album Art things can get problematic).


yeah, dread...devs have to serve a lot of masters and as Bex and Techno posted above- [b]make it user configurable[/b]...with whatever configuration is deemed best for the new user as default. Choice for the user is ultimately the best solution. For those of us with large libraries MM is the ONLY choice.

After reading this thread, I find the suggestion of Teknojnky a good compromise(is this word correct?).

As has been mentioned already, having the root library node populate with all library tracks has long and often requested feature and source of confusion for many new mediamonkey users.

However, I also agree with cmx, that this feature with very large libraries can cause an un-necessary delay/freeze of MM while it loads the track list.

I suggest that this simply be added to the library options: Show all tracks in library node (check/uncheck)

Another potential option would be, to make F7 collapse the tree without changing the current node.

BTW, cmx I also suggest you run maintain library if you have not recently. I run mm3.1 on my laptop (dual core 2.0 ghz) and it does not peg either core when doing F7, but 1 core is about 50%.

My 3.1 library database is ~650 megs with ~150k tracks @ ~1.2 tb.

[quote="cmx"]

Nyn, I use NO scripts...just too much complexity and a batch of maintenance issues from past experience. Here, simple is best, and MM has provided basic, complete and logical functionality that has made simplicity possible.[/quote]

:lol: :lol: What was that you said about one person's simplicity is another's mess? For me scripts are required for me to maintain simplicity...

Nyn

What she said Bex...lol..the function of the "Collapse" function has been perfect for me up till now. Would serve no purpose for me focusing on the Location node.

Nyn, I use NO scripts...just too much complexity and a batch of maintenance issues from past experience. Here, simple is best, and MM has provided basic, complete and logical functionality that has made simplicity possible.

I actually incorrectly thought that the Location Node was unhidable so my suggestion isn't possible to implement...

[quote="Bex"]
Also pressing F7 (=Collapse the tree) shouldn't set the focus to the Library-Node but the Location-Node instead, for obvious reasons.

I added this to Mantis:
http://www.ventismedia.com/mantis/view.php?id=2570[/quote]

Bex:

I do not know if the Location node is a viable option to set as the default. Personally, I have the Location node turned off in all of my filters because I never use that node. With that in mind, what would that do to my navigation??

Nyn

CMX:

I always find it fasinating to read how other users use MM to meet their needs. First to answer your questions, no I do not use the navigation toolbar, I only use the tree navigation itself. Also because I have become VERY accustomed to using scripts I use Onenonymous' [url=http://www.mediamonkey.com/forum/viewtopic.php?t=26383%20]Right Click for Scripts[/url] script to customize the Now Playing and Standard toolbars for the particular scripts that I use for my daily use. I also use MoDementia's [url=http://www.mediamonkey.com/forum/viewtopic.php?f=2&t=32273]View Manager[/url] script to easily jump between my filters and custom views. So for me I rarely use the navigation tree itself because I can just pop up the particular view that I want. But when I do need to use the navigation tree, the Title node is the node that I use for viewing of my entire library. Unfortunately I have yet to find a script that would COMPLETELY collapse the tree when I have expanded it for whatever reason.

Also, let me add while I am thrilled the devs have made some toolbars customizable, for me the thrill is in the fact I can turn off MM shortcuts to make more room for my custom shortcuts. I only have the Standard, Search and Now Playing toolbars active, all others are turned off. Everything I need is either customized on my toolbars or the Right Click menu. Have I mentioned how lazy I've become with these conveniences??

As for the debate regarding whether the main node should contain all the tracks, I'm sure you will get good arguments for both sides. So yes I do believe this should be configurable. If only it was possible to turn this feature on/off. But I also agree the main nodes should have consistent behavior, but I am not vehemently for or against either option since this is not a feature that I regularly use or need.

Also, let me say this. I've read alot of comments from users who want and have demand alot of custom functionality to be available natively. For me, I am not that concerned that features/requests are delivered natively in MM. If I can get what I want via scripts, plugins or skins that I am content. There are many features available in MM that I do not use and have never used, but that does not mean they should be removed because they are useless to me. I LOVE the fact that MM allows it's users to create customizations to meet individual needs. I have never used a program that I have enjoyed as much as I do MM, but I digress.

As far as this feature, I do not know if the devs will go back to the way things were or continue with these new changes, but either way I will find a way to "workaround" it because I am not ready to give up using MM.

Nyn

nyn thanks for the thoughtful post. Always good to advance the discussion. When I discuss something here concerning MM use, I try to keep in mind the functionality for ALL users...consistent logic and user choice is always the best. By changing the behavior of individual nodes to meet specific user's tastes at the expense of others...I think that is going down the wrong road..did someone say iTunes?

Yes I agree, the behavior of the "collapse tree" icon/function button does not seem logical- IF you equate the "Library" node to the "Web" node or "Net Radio" node or "My Computer" node...BUT it IS logical as far as Tree Navigation of the actual music files on your computer and in your "Library" is concerned if you consider it the "Root" node as I do... below I suggest a possibly better solution for all. (BEX defaulting to "Location" node doesn't seem the most logical for all users either)

If you ONLY want to see a full listing of all tracks, and you want to do it quickly and easily, I think that is totally legit. Its not the way I happen to use MM right now and by having the "root" of the nav tree display all tracks it actually bogs down the system and makes it difficult for me to navigate and work with my library...it is a devolution. One question too...are you primarily using the "Navigation Bar" or the Nav Tree itself? I am referring primarily to the function of the Nav Tree itself.

I suggest the devs make ALL "first tier" nodes operate ubiquitously as the Library node did previously- TO JUST display child nodes NOT all files of all child/sub nodes. It is simply not practical nor logical to have the tree operate otherwise and it is clearly confusing when different nodes respond differently.

To gives users choice and control I suggest the Devs make Nav Tree Toolbar buttons available for ALL nodes that would allow a user the open the child node of user's choice with ONE CLICK. This is something I have been looking forward to with the new toolbar customization ONE CLICK ACCESS TO ANY NODE....but is not available on the Nav tree toolbar.

I like things clean and simple too nyn...but one person's clean and simple is another's mess. [b]DEVS[/b] give us choice and the ability to customize...with this you can implement a simple "default" configuration for new users that addresses the learning curve and the needs of what you determine to be the "consensus" without disabling or downgrading MM itself.

Hopefully this discussion can continue positively and with suggetions and solutions that benefit all users.

I think this new feature is useful for new users but it should be configurable.
Also pressing F7 (=Collapse the tree) shouldn't set the focus to the Library-Node but the Location-Node instead, for obvious reasons.

I added this to Mantis:
http://www.ventismedia.com/mantis/view.php?id=2570