Skip to main content
Topic: Library Tree Discussion (Read 33755 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Library Tree Discussion

Reply #50
Library v 1.1 & JS Smooth Playlist
For example, I create a new - with the name "My new playlist," and make it active.
  If  send folder through the menu Add to Current Playlist, instead of adding to the Current ( "My new playlist"),
  the addition will always be in the "Library view"

Insert in Current Playlist - work correctly .

Re: Library Tree Discussion

Reply #51
^ I still can't reproduce & so the issue is unconfirmed. I tried by creating a new playlist in both sim_playlist manager and JS Smooth Playlist, activated the playlist and used the library tree menu "Add to Current Playlist". Items were always correctly added to the new playlist. I've repeated it many times without issue, on two different foobar2000 set-ups. I assume you don't inadvertently left click first, which may activate library view resulting in "Add to Current Playlist" then using that playlist...

@du22y I can reproduce that issue & believe I have fixed it in my version. The fix should be in the next release

Thanks for the feedback

Re: Library Tree Discussion

Reply #52
@WilB
Awesome !
Thank you for your hard work  ;) .

Re: Library Tree Discussion

Reply #53
 
Quote
I still can not reproduce & so the issue is unconfirmed
:-[  I all the same used in the old version ...
  @version "1.1" all is well

Quote
The fix should be in the next release
and this please:
Quote
1 .If turn on "All Music" and collapse the tree -
list disappears.

Hope for the "Node" is a decision on the size of the change  +  and  - icon :

Re: Library Tree Discussion

Reply #54
Hi!

Thank you for your excellent script! It is very usefull!
Only one question : Can we use it for other playlists except from music library?  Lets say I want your script to list my "Chopin playlist" with all the items I have in this particular list. Is this possible?

Re: Library Tree Discussion

Reply #55
@seriousstas: I had already fixed/implemented those (and point raised by always.beta) in my version

@sstavross: It's a library viewer and so doesn't read data from playlists

However, you can type, e.g. "Chopin" without the quotes in the search box, to have a tree view of the tracks

Or you can create a filter for the library that's permanently available, e.g. use query "Chopin" without quotes. Such a filter would work like an autoplaylist for "Chopin" since its updated when the library content changes + offering the advantage of a tree view of the contents

Re: Library Tree Discussion

Reply #56
New Version: Library Tree 1.2

CHANGELOG

Added configurable "Node: Size" & "Scroll: Smooth Scroll Level..." that may help touch device users (panel properties)
Improved interaction with playlist, especially when using Ctrl key
Fixed Allmusic node collapse regression
Fixed search paste issue with long search text

Library Tree 1.2

Re: Library Tree Discussion

Reply #57
Thank you so much !
"Node: Size" - I would hope to change the icon size, and not just distance.
Quote
  that may help touch device users.
  For work on a touch device - moving playlist should be a mouse with holding down the left button.
"_PROPERTY: Touch control" in "JS Smooth Playlist"  Then it emulates the movement of a finger.

Re: Library Tree Discussion

Reply #58
Hi, really enjoying the library tree script so far myself.

There is one small thing I noticed while playing around it a bit more, and it is that the mouse scrolling behaves in a bit weird way when more elements are collapsed. So instead it scrolling the default amount (usually 3 lines at a time) down, it scrolls by some really big amount at a time. And it only happens when the nodes in the tree are collapsed outwards, while on the root level the mouse scroll is completely fine.

edit: actually it doesn't seem to be fine even on root level, but more to do with how much of the tree is on the view and how much is not. So when the visible area gets small enough the scroll seems to broke and scroll way more than it should on single scroll up/down.

Re: Library Tree Discussion

Reply #59
I couldn't reproduce any scrolling issues & no one else has reported any. By default the script uses "Page Scroll" and so will scroll by a large amount, depending on the info to be displayed etc. You can set "Scroll - Mouse Wheel: Page Scroll" to false in panel properties for standard 3 line scrolling. I hope that helps.


Re: Library Tree Discussion

Reply #61
I couldn't reproduce any scrolling issues & no one else has reported any. By default the script uses "Page Scroll" and so will scroll by a large amount, depending on the info to be displayed etc. You can set "Scroll - Mouse Wheel: Page Scroll" to false in panel properties for standard 3 line scrolling. I hope that helps.
Oh I never noticed that page scroll option there, would have probably checked that if I had any idea there was option for it. So anyways thanks for the info, that did indeed solve the scroll issue I was having.

Re: Library Tree Discussion

Reply #62
@TheQwertiest: The left button single click seems to work the same way as DUI album list; i.e. with both library tree & album list the playlist is populated on single click. I don't see the advantage of having to use an extra click (double click) to accomplish this, but maybe I am missing something... It would also mean that single click would do nothing upon clicking on a name unless set otherwise. Bear in mind that if single click was set to do something else, that action would also run on double click, which may lead to unwanted events. Anyway, for me to consider it further, please provide convincing arguments as to why you want the double click option, why single click isn't suitable, what benefit double click offers and if added whether you want any other actions also triggered, such as starting playback
Well, it's my attempt to make foobar behave more Winamp-escque =)
My usage scenario is quite simple - I use Library Tree as 'file' browser (Library View PL is used as a simple playlist, that is populated only via double-click or manual addition). I.e. I can freely move through directories\playlists and etc without worrying, that my playlists might be emptied or changed. That's why I want to avoid 'send to playlist' via single LMB click.

Your script is the only one that I could 'force' to behave like that (+ it's stylish and suits my foobar's theme), so I was hoping, that it would be possible to implement it as a build-in feature, as to avoid patching it manually every release.
Bear in mind that if single click was set to do something else, that action would also run on double click, which may lead to unwanted events.
Yeah, forgot about that... I guess it might be impossible to implement my request while retaining all the other functionality without changing a lot of code :\

Re: Library Tree Discussion

Reply #63
@TheQwertiest: The left button single click seems to work the same way as DUI album list; i.e. with both library tree & album list the playlist is populated on single click. I don't see the advantage of having to use an extra click (double click) to accomplish this, but maybe I am missing something... It would also mean that single click would do nothing upon clicking on a name unless set otherwise. Bear in mind that if single click was set to do something else, that action would also run on double click, which may lead to unwanted events. Anyway, for me to consider it further, please provide convincing arguments as to why you want the double click option, why single click isn't suitable, what benefit double click offers and if added whether you want any other actions also triggered, such as starting playback
Well, it's my attempt to make foobar behave more Winamp-escque =)
My usage scenario is quite simple - I use Library Tree as 'file' browser (Library View PL is used as a simple playlist, that is populated only via double-click or manual addition). I.e. I can freely move through directories\playlists and etc without worrying, that my playlists might be emptied or changed. That's why I want to avoid 'send to playlist' via single LMB click.

Your script is the only one that I could 'force' to behave like that (+ it's stylish and suits my foobar's theme), so I was hoping, that it would be possible to implement it as a build-in feature, as to avoid patching it manually every release.
Bear in mind that if single click was set to do something else, that action would also run on double click, which may lead to unwanted events.
Yeah, forgot about that... I guess it might be impossible to implement my request while retaining all the other functionality without changing a lot of code :\

Hi TheQwertiest, could you share the complete code with singleclick autofill disabled? I can't make it with your past instructions, Thanks!

Re: Library Tree Discussion

Reply #64
@TheQwertiest & @condenado

Just to confirm that I had already added the ability to disable single click auto-fill in my copy. When single-click auto-fill is disabled, the playlist will be only be filled on left double-click or manually.

There will be a new a release shortly incorporating this feature, when I have finalised a request from always.beta...

HTH

Re: Library Tree Discussion

Reply #65
@TheQwertiest & @condenado

Just to confirm that I had already added the ability to disable single click auto-fill in my copy. When single-click auto-fill is disabled, the playlist will be only be filled on left double-click or manually.

There will be a new a release shortly incorporating this feature, when I have finalised a request from always.beta...

HTH

Perfect!! I'll be waiting. Thanks WilB.

Re: Library Tree Discussion

Reply #66
There will be a new a release shortly incorporating this feature, when I have finalised a request from always.beta...
I am glad to hear you say that you are adding a feature I want. Thanks WilB. Can you share a modified version? Its appearance (scroll bar) is similar to Br3tt’s JSS~.

Re: Library Tree Discussion

Reply #67
Hi,

This component is greatn thank you
A suggestion : For each node, can you make the whole line clickable instead of just the text ? maybe it can expand the node when the mouse click is before the node's text, and it can send to playlist when the click is on the node's text, or after the node text.
It will make the script a little more intuitive to use.

Re: Library Tree Discussion

Reply #68
Hi,

This component is greatn thank you
A suggestion : For each node, can you make the whole line clickable instead of just the text ? maybe it can expand the node when the mouse click is before the node's text, and it can send to playlist when the click is on the node's text, or after the node text.
It will make the script a little more intuitive to use.
It's okey, i managed to update the script myself. One last thing which would be great is to expand the nodes which match the search string, when performing a search. I tried to do it also, but it require a good understanding of the code, and probably significant changes, so i gave up.

Re: Library Tree Discussion

Reply #69
@collagen I have added the requested features and they will be in the next release.

@always.beta Your requests will also be in the next release.

Re: Library Tree Discussion

Reply #70
New Version: Library Tree 1.3

Thanks for the feedback.

CHANGELOG

ADD: Ability to disable single-click auto-fill of the playlist. When disabled, the playlist can be filled manually, from the menu, or on double click. Set in panel properties; "Text Single-Click: AutoFill Playlist" and adjust "Text Double-Click" according to taste.

ADD: "Expand" (right click menu): fully expands node (N/A for large nodes).

ADD: "Collapse All" (right click menu).

ADD: Auto expand search results. Operates when list is refined sufficiently – see technical notes below. Default is off.  Enable in panel properties: "Search Results Auto Expand".

ADD: Improved custom node icon options, e.g. chevron arrows like >. To use, enable "Node: Custom..." in panel properties.

ADD: Improved navigation. Node selection area is bigger + nodes highlight on hover (can be disabled). Additionally, active text area can be increased by enabling "Text Whole Line Clickable" in panel properties.

ADD: Node size can now be zoomed (mouse-over > Ctrl + Alt + mouse wheel).

CHG: Zoom. Ctrl + Alt + mouse wheel are now required to zoom the font, filter and node sizes on mouse over. This is to stop ctrl selection of tracks while scrolling sometimes causing zooming.

ADD: Custom node colours (panel properties).

ADD: Customisable scrollbars (panel properties).

FIX: Minor draw issues.

Technical notes

1) The menu "Expand", and search results "Auto Expand", have default limits of 500 & 350 tracks, respectively. This is for efficiency reasons & because expanding to large lists impedes navigation. Thresholds can be changed in: "ADV.Limit..." in panel properties.

2) Availability of custom icons may depend on fonts installed. The icon font can be set in panel properties. Font symbols can be pasted in.

3) Ensure comma "," separators are retained where used in panel properties.

4) Some panel properties have changed & redundant removed (view & view filter patterns unaffected). Export panel properties, before updating, if you need a record.

Re: Library Tree Discussion

Reply #71
New Version: Library Tree 1.3.1

CHANGELOG

Fix: Draw regression

Re: Library Tree Discussion

Reply #72
Thanks. Finally i did it myself on my custom library tree, but a little bit differently : on my script, when there is one node only at any level of the tree, this node is automatically expanded. Like that it work for the search results, but it also work when an artist have only one album, when you expand the node of this artist, you see directly the tracks of the album.
I added a property called autoExpendOnSingleChild, and i added the line of code below at the complete end of the function named "branch" of the object "populate".

if(br.child.length==1 && pop.autoExpandSingleChild) pop.branch(br.child[0]], false , true);      

Re: Library Tree Discussion

Reply #73
Hi Wilb. Firstly many thanks for a great component and it keeps getting better.

I have found a small problem with the following view;

View by Genre // %<genre>%|[%band% - ]%album%|[[%discnumber%.]%tracknumber% ][%track artist% - ]%title%

As you should see I use multi-value genres.

I get a crash popup window telling me that at line 583 Col 93. 'Unable to get property 'name' of undefined or null reference.

It may be my inconsistant tagging but I wouldn't expect a crash.

Re: Library Tree Discussion

Reply #74
New Version: Library Tree 1.3.2

CHANGELOG

FIX: Regression in multi-value tag handling

 
SimplePortal 1.0.0 RC1 © 2008-2019