Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Library Tree Discussion (Read 127926 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Re: Library Tree Discussion

Reply #326
@WilB
I found an annoying error in the script (I think so). If the tag field name contains the character ⧸ it automatically gives a pause to the tag (see screen). If instead of ⧸ I use / this problem does not occur.

My sample code
Code: [Select]
[ ($and($meta(LABEL),$meta(CATALOG NUMBER)),'['%LABEL% %CATALOG NUMBER%']',$if2(['['%LABEL%']'],['['%CATALOG NUMBER%']']))]

Library Tree 2.1.3
Please take a look at it

Re: Library Tree Discussion

Reply #327

@osenboz

I suspect its because the track number isn't padded in the filename.
i.e. they're 1, 2, 3, 10, 11 etc as opposed to 01, 02, 03, 10, 11 etc
I could see the issue. DUI album list behaves the same way.

The order is determined by OrderByRelativePath() which I have no control over.

%tracknumber% that's used in view by album automatically pads.

Library Tree also does a display sort for displayed text strings which has full numeric handling and so all displays in the actual tree correctly. But using that string sort on the whole library instead of OrderByRelativePath() doubles the initialisation time and likely wouldn't be compatible with the condensed style that OrderByRelativePath() produces.

I always pad track numbers in filenames.

@TheQwertiest

Thanks. It looks nice!

Re: Library Tree Discussion

Reply #328
@angriestchair

As far as I am aware dialogue boxes aren't an in built feature of Spider Monkey Panel. So they would need coding from scratch which is a lot of effort. If there was some generic code that could be used may be in due course.

The next version will have a settings button which may help.

Sorry but the other feature isn't supported.

@Tropoje

Sorry but looking at your picture I can't see what the problem is. I tried that character quickly and all seemed OK.


Re: Library Tree Discussion

Reply #330
Well I reproduced it with 1.3.1 beta...

Re: Library Tree Discussion

Reply #331
@WilB , you can use HTML to create dialog boxes via ShowHtmlDialog. Of course, one would still need to write the whole dialog, but it is much easier (IMO) than doing it through ActiveX.

Re: Library Tree Discussion

Reply #332
If there was some generic code that gives a nice tabbed dialogue box, so one can easily just changes the entries  in a manner analogous to panel properties then may be.

For the time being I suspect that the new settings button in the next version will suffice.

Re: Library Tree Discussion

Reply #333
@WilB, osenboz's problem was the following: 10, 11 ... 20, 21 was sorted as 10, 20, 11, 21 ..., which was caused by a bug in SMP v1.2.3 that resulted in the first character of path to be ignored during sort.
`OrderByRelativePath` (bugs aside) uses the same algorithm as Windows file explorer (hence the usual 1, 10, 11... problem).

[EDIT]: Judging by the bug report, osenboz actually has a proper padding for track numbers, so they won't be affected by Windows sorting problem either =)

Re: Library Tree Discussion

Reply #334
If there was some generic code that gives a nice tabbed dialogue box, so one can easily just changes the entries  in a manner analogous to panel properties then may be.
I'm gonna be tackling that idea very shortly, but no promises on the results. The biggest issue will be dynamic sizing of the dialog which may not be possible.

Honestly might be better to just start with some text/checkbox style controls and just draw them in an on_paint. That gives the most flexibility. but also involves the most coding. You've already done some of that work with your search input, so I might go down that route for a bit and see where it leads, if the HTML stuff proves to be too much of a pain.

Re: Library Tree Discussion

Reply #335
@TheQwertiest @WilB
Thanks a lot for your updates! (since my file-namings are properly padded, updating to SpiderMonkey Panel v1.3.1 solved the problem!)

Re: Library Tree Discussion

Reply #336
Thank you for this component, it's very fast! I love the now playing filter feature.

Feature idea/request: allow specifying multiple tags at the same branch level that will create multiple entries. This is a feature of Facets. For example the first tree level could be %<artist>%OR%<album artist>%, where OR is some divider. Then under the The Beatles node, for example, you will see albums where album artist = The Beatles, and also any tracks where artist=The Beatles from other albums (without duplicate entries where album artist == artist == The Beatles)

Re: Library Tree Discussion

Reply #337
@ubercow

Quote
Thank you for this component, it's very fast! I love the now playing filter feature.

Feature idea/request: allow specifying multiple tags at the same branch level that will create multiple entries... For example the first tree level could be %<artist>%OR%<album artist>%, where OR is some divider. Then under the The Beatles node, for example, you will see albums where album artist = The Beatles, and also any tracks where artist=The Beatles from other albums (without duplicate entries where album artist == artist == The Beatles)

I've added a soft splitter to my copy that should do what you want. It should be in the next version unless anything unforeseen arises.

It seems to work very well, and for example in a simple form also allows combining album artist & artist style views into a single view:

%album artist%¦%artist%

1) Tracks on compilations are kept together by grouping under Various Artists
2) Artists on compilations also display under the artist name

Both display on the same level.

[moved discussion to correct location]

Re: Library Tree Discussion

Reply #338
^ My favorite feature from Facets. This is brilliant! Thanks WilB. :)

Would it work with splitting multi-value tags?  %<genre>%|%<style>% (using the angled brackets)

Re: Library Tree Discussion

Reply #339
Yes

Re: Library Tree Discussion

Reply #340
@WilB
I am using Eole app with with a lot of customizations which makes it difficult to just update without a lot of work. My problem is something like  $replace($directory_path(%path%),\,|)|%filename_ext% dont work. Could you post that part of your code that changed from about v1.3.3 to v1.3.6 to make it work. Thanks

Re: Library Tree Discussion

Reply #341
@WilB
I am using Eole app with with a lot of customizations which makes it difficult to just update without a lot of work. My problem is something like  $replace($directory_path(%path%),\,|)|%filename_ext% dont work. Could you post that part of your code that changed from about v1.3.3 to v1.3.6 to make it work. Thanks

Nevermind I found it

Re: Library Tree Discussion

Reply #342
Hi @WilB , testing Library Tree right now :)
So far so good, but I have noticed a glitch maybe :
In Panel Properties, if I change _CUSTOM COLOURS/FONTS : USE from False to True, all results disappear, regardless of what I put in _CUSTOM COLOURS/FONTS : EMPTY = DEFAULT (e.g. 255-0-0). Playing a new track doesn't solve the issue.

My goal would be to keep the same font, but change its color and make it bold instead of regular. Is that possible ?
Also, I would like to know if I can rename the "All Music" to something else. Thanks !

Re: Library Tree Discussion

Reply #343
@WilB don't know if you saw the note from @snotlicker on known issues at JScript Panel V2.5.0 b4 with Library Tree (see here). Any chance to still maintain Library Tree as well for JScript Panel (e.g. for Georgia)?

Re: Library Tree Discussion

Reply #344
Georgia is being updated for SMP so you should wait for that.

Since it's a single panel layout, it's not trivial to integrate any updated version of Library Tree in to it. The developer of Georgia won't do it and no one else would know how even if they wanted to. It's very complex as opposed to going in its own panel. Another aspect of it being single panel is that you simply don't need the latest version of JSP. If you don't have the skills to read the changelog/breaking changes wiki page and fix it yourself, you're not going to gain anything else from running the latest version.

edit: I've attached a fixed version for Georgia which goes in js\CaTRoX_QWR

I'm not fixing the standalone version because the SMP version is far superior. It's one of the few scripts that actually benefits from the faster internals provided by the Mozilla JS engine and I believe its sorting mechanisms have been optimised as well. Since JSP now requires Windows 7 like SMP does, there is no reason not to use it.

Re: Library Tree Discussion

Reply #345
@snotlicker: thanks very much!!
Adapted 2 lines, 2558:
Code: [Select]
n = lib_manager.node[pos][l]; else
and 3672:
Code: [Select]
p.pos = get_pos; else
now seems to run stable on JSP 2.5.0 b4 including embedded Library Tree. Shows only CD art in my case, but for now that is great for me!
For stand-alone Library Tree, I am already on SMP.
Thanks again for continuously developing JSP!

Re: Library Tree Discussion

Reply #346
Yes I have JSP compatible version done. It should be released in the next round of script releases.

 

Re: Library Tree Discussion

Reply #347
It should work. I tested & it seemed fine.

All the custom handling has changed in the next version anyway & so it will be much easier to change.

Options > root node > view name enables use of the 'view name' which is configurable. Again all this will be much easier in the next version.

Re: Library Tree Discussion

Reply #348
All the custom handling has changed in the next version anyway
Let's just wait for the next version then, no worries. Any ETA ?

Re: Library Tree Discussion

Reply #349
You really shouldn't bother with a JSP version. As mentioned a few posts up, newer versions of JSP require windows 7 just like SMP so all users of your scripts should be on SMP by now. Even the Georgia theme has a SMP version now (currently beta but should be released fully soon).