RELEASE 1.6.5

playlist tree playorder thingy plays in __treeplay__ playlist (does not overwrite current playlist)

lstrcpyn -> safe_strcpy ==> faster (lstrcpyn always copies N bytes)

changed bold changing action from control-click to control-shift-click

redid context menu playlist options

redid double click options - your old settings will probably not be right

options:
config: shift double click
config: control double click

Try putting %__codec%| at the beginning of the format string. You should get all the files grouped by codec and then by anything else you like.

Thank you very much for those double click extensions. Any hope to have a "remove from active pl", one day? (I don't even know if it is possible but asking is free, so...

I'm not sure I understand your first two sentences: do you mind explaining a bit more, please?
And what does that "process local shorcut keys" mean? exactly?

Thanks again.

Process local shortcut keys refers to some shortcuts keys in the playlist tree such as 'M' (brings up context menu), 0-9 (set expansion level of node), C-up (move up) C-down (move down). You can now turn these off.

Previously, if you were using playlist tree for your play order in the drop down, it would overwrite the current playlist with the item it was going to play. Now it uses a seperate playlist so your lists won't be affected.

So if you double click on a node, it will remove every track in that node from the active playlist?

Interesting...

... very interesting, and useful, I think.

Some times my double clicking hand is faster than my brain (you know, after all that OK Corral stuff...) and when it manages to wake up (the brain) just finds out that too many tracks are gone to the playlist. So, to not break the "stream of selection" it would be nice being able to just shft + double click to remove the unwanted without having to go to the right pane, select and remove.

CBOWRON, you are seriously so awesome... You have created, by far, the best mp3 databasing program that I've ever seen.. and I admire that you're still perfecting it.

There are still some things missing that I must reiterate (now that I know you're in full development swing)

Column Sorting in Playlist Tree Browser (already said that, but I think it's a pretty important one)

Drag and Drop from Playlist Tree Browser (also have said that in the past, haha)


oh and I thought of another thing that would be handy.... perhaps adding an "insert into playlist" option in the double click menus... I suppose adding drap and drop would solve the need for this... but if that's much harder to implement, than perhaps this could be another option (?)




Anyway... those are all suggestions.


Seriously though... Great plugin... you can't be told enough what a good job you've done on this.

may be I explain myself not specific enough. I do have already listings by codec, but....
if there are mp3 and flac available, I only want to see the flac, or maybe only the flac files are added to playlist in case, that I add...

You should play with the $if variable, I'm on holidays so I can't help (my brain is also on holidays ) but I'm almost sure you could achieve what you want.

thx for the hint, will check it out...have a great vacation, I am jealous

RELEASE 1.6.6

TreeViewHook clean up

tree drag and drop code changes (nothing user visible)

menu code changes (nothing user visible)

limited sort in browser
- click on a column header to sort by that column
- only sorts descending
- sort criteria is not saved between nodes
- when a node is selected it will be displayed in the browser in the order in the node

Drag and Drop *FROM* browser

I don't think I need to say I love you again.

It appears that when an item is being dragged into the playlist from the browser window, the playlist tree window begins to scroll rapidly down... I'm sure you caught this, but it's the only bug I've seen so far.

The column sorting is awesome.. This thing is nearing total perfection, imo.

RELEASE 1.6.7

$playlist() command - like $drop but from a playlist

Fixed some drag and drop scrolling issues

I'm back in the development swing of playlist tree and I'm interested in hearing ideas for new features. If you have some ideas please let me know here, or preferably at the playlist tree forum http://bowron.us/smf/index.php.

Even if you've posted the feature request before, post it again or bump the thread so I know what people are still interested in.

Bug reports will also be investigated.

Hey, just installed this plugin yesterday and I'm liking it a lot. I have 2 requests -

1) The Process Local Shortcut Keys option seems to disable the custom shortcuts for Playlist Tree, but it still processes my other keyboard shortcuts. Would it be possible to add an option to not process any keyboard shortcuts, like in the Album list panel?

2) When I have the Album list panel in the sidebar, I can press the Tab key to move focus out of that panel and back to the playlist. In Playlist Tree, Tab appears to have no effect. Would it be possible to add this functionality?

No one?

You can hide the root node in the Appearance options to get the effect of multiple top-level nodes.

Can you please fix the incorrect handling of apostrophes. When using for instance $playing(%album%) and %album% contains a ' , a tagz syntax error is generated.

Why when I use this plugin does my fb2k memory usage increase by two-fold (20mb)?

disable icons... I find that those tend to boost the memory usage a lot. (besides, album list doesn't even have the option of icons, and I think they're a little superfluous to begin with... they're nice though)

So I write you again my last problem :

Hello, I have some questions about format problems :

- I've tryed to use :
"$cut(#artist#,1)|#artist#|'('%date%') '%album%|[%disc%.]$num(%tracknumber%,2) - %title%"
The problem is that format don't work with artists with an ' in the name. What can I do?
These entryes are displayed as "[SYNTAX ERROR IN FORMATING TREE]"

- I've tryed to use :
"$if(%album artist%,$cut(#album artist#,1),$cut(#artist#,1))|$if(%album artist%,#album artist#,#artist#)|'('%date%') '%album%|[%disc%.]$num(%tracknumber%,2) - %title%"
But with this format I have just file having %artist% AND %album artist% tags in the result... i don't understand!

....mmmh........ just started rubbing my hands while thinking what to put in my list..........

Apart joking: would you prefer having a list in one post or each request on its own post?

Thanks for sharing your energy and resources just to make other people world a little easier (and so, better).

Hi,

One of the things I'll really love is the possibility of using hotnessscript into PT. But as PT seems to handle Globals in a different way that Column Ui (the script is made for that component) I've been trying in the past to 'port' the script to PT globals (see here) without luck.

I'll really like to be able to use this script in PT, and display the info in the PT browser and use it as a sorting criteria in a node (to create a hotest tracks).

Any help, tips, ideas, or changes in this component to allow this kind of stuff will be greatly appretiated

thanks.

If the requests are similar in nature or a set of requests that are related post them together, otherwise please start a new topic for each request.

Please post the requests at http://bowron.us/smf/index.php

What version are you using? This seems to me to be working in the current version.

EDIT: If you are using the current version, please post your query.

I was using an old version (1.4.n) now with the last version I don't have ' problems, cool

RELEASE 1.6.8

double click option: play (plays track/first track without affecting any playlists)

context menu: bold.../unbold all

menu option:Components/Playlist Tree/Settings.../Show Hidden Nodes
if you use the menu option it should refresh the tree, hiding or unhiding all hidden nodes

option: appearance:Show nodes with hidden content
if disabled nodes with hidden content will not be in the tree. (lets you really hide a single node)
(requires restart for it to affect the tree if you do it from preferences menu)

sort ascending and descending in browser (first click descending, second ascending)

Nice new options, thanks

RELEASE 1.6.9

fixed some drop source feedback

@limit<n> - limits the number of subitems in a node
- can be used in a query. the following will limit to 3 tracks per album
%artist%|@limit<3>%album%|[$num(%tracknumber%,2) - ]%title%

the format @tag<x> is being used because it does not interfere with the normal fb2k formatting strings. at some point, ALL local functions may be converted to this format.

Which tracks? The first three in filename alphabetical order or the first three in the next level tag order (in this case tracknumber), or according to the sorting string (if any)?

Is there a way to get the three tracks randomly?

Would this @limit<3>%artist%|%album% pick three albums or three tracks too? If the last, from which album?

Thanks.

The first three items that make it in there based on sort order.



3 albums. The limit refers to the number of subitems that a folder can have. In your example each folder can have at most 3 subitems which in your case are albums.

this @limit<n> is excellent!

So, as i was saying in the other forum, a same limit on total time or total size will be prety cool.

I'm discovering $node() and $drop() functions, they are very very cool!!!!

the possibilities of PLT are very powerfull with these functions.

So, I have one question, what happend with $node() when i have multiples queries with the name called by the function?
There is a way to specify full nodes path to this query?

An other question, when i use $node(), are the data stored two times into each of the two queries trees? I think, there is an advantage of time to parse the database using this function, but there is too an advantage in memory taken by the query tree?

I'm quite sure the answer is "yes" but let me ask all the same:

can I nest that @limit function one into the other?

I mean, can I create something like this:




to get 2 tracks from each album of different 10 artists under the genre jazz?

Thnaks.

(Go to testing while waiting for your answer....he,he....)


Edit: mmmh, getting some crashes. Probably I was too optimistic..., wasn't I?

You should be able to. I will look into it to check out the crashes.

RELEASE 1.6.10

fixed bug in quick query in compound queries using MISSING

fixed crash on @limits on subfolders rather than leaf nodes in queries

option: config: Process menu options when not in focus

Thanks... works just as I had hoped.

RELEASE 1.7.0_beta1

internal changes to search all results

@playlist, @node, @notnode and @drop allow for queries.
example - will return all the tracks in Favorites playlist by the Beatles:
query string: @playlist<Favorites> artist HAS beatles
[x] foo_playlist_gen_ex

if you do not want to have it filter anything, just have the @tag<> and check
the foo_playlist_gen_ex button

massive changes to local tag handling. internally all local tags such as %name%, %size%, etc
will now be %_name%, %_size%, etc. code has been inserted to make changes as necessary
but in the future please use the %_tag% in your own codes. It should have been like this
from the beginning but I did not see that then. Sorry for the convenience. (includes
%_julian%, %_julian_frac% and %_systemdate%)

All titles will now be formatted using the title formatting. No more $format(). This also
means that some codes will have to be quoted to get them to work.

%searchstring% = %_searchstring% for search results

%length% => %_ptlength%

%default% => @default (for @drop formatting and query sorting)

local functions converted to @fn<n> format. This includes:

@drop<>
@node<>
@notnode<>
@playlist<>
@refresh
@nosave
@force
@nobrowse
@icon
@ex_icon
@playing<>
@first<>
@sum<>
@avg<>

globals are off for the time being...

Wow!

Due to the major changes, it would be very useful being able to run two instances of PLT - the last old one 1.6.9 and the new 1.7.0 - side by side: is it possible or we have to run two instances of the whole FB copying and renaming the FB dir?

Another thing would be a bit of documentation or a couple examples for each function or command. Where the fn has changed, it would be useful having the before and after examples. If you can think of a way, we (at least I...) could help you putting this together, maybe one fn at a time.

If docs is not possible at the time, at least having an up to date list of all the commands and functions and their sintax so we can experiment with them and build the docs by ourselves.

Thanks.

I can't go into serious details right now, but basically anything that was PT specific and used the form $tag() now uses the the form @tag<>.

And all the tree specific %tag%'s are now %_tag%. But the old style should still work for these for now.

Just installed it.

I have $icon(xx) or $ex_icon(xx) after the title of almost every node and if I open the edit box I can see those strings added to the actual title in the label box.

right. those need to be converted to @icon<xx> and @ex_icon<yy>

Sorry but I don't understand you.

I'm not using any icon in the tree nor any $icon anywhere (if this make sense...).

For now I reverted to 1.6.9. If I can to do something to solve that by myself please tell me, if you have to do something to fix it don't bother answering this one: I will wait for the fixing.

every where you see $icon(xx) change it to @icon<xx> and everywhere you see $ex_icon(yy) change it to @ex_icon<yy> in the titles and such.

Those code get put there when you change icons, either by adding the tags yourself or by changing the icons by the dialog boxes.

1.7.0beta 2 will have some automation of the conversion process so you may want to wait for that.

Sure.

Thanks.

I'll wait for that then

Thanks for the new build, I'm having my PC back in today or tomorrow so I'll be able to test PT. It seems that there's some major internal changes down there.

RELEASE 1.7.0_beta2

$left => @left, $center => @center, $right => @right in browser alignments in columns

some internal conversion of $tag() to @tag<> when loading

No more icon issues but it sets the sorting method of all the nodes to "custom" "%default%".

?


My FB startup time has decreased from 25 secs to 18.

!


The total refresh still takes 25 secs.

.

RELEASE 1.7.0_beta3

reintroucded @format<> tag - use it in folder names when the something in the name needs to be evaluated... example usage in a query format string:

<'@format<%_itemcount%>'> [%album%]|[$num(%tracknumber%,2) - ]%title%

convert tags in m_query_sort (sort criteria will now be converted from %default% to @default