edit : More generaly, it would be useful to have "clickable" buttons in Trackinfo, for exemple if you display stars to chow your rating, you could make each star a button which would allow you to quickly set your rating. Or is it already possible ?

Yeah, I think that and the ability to control volume through Track Info Panel in the same way would be just perfect. I mean right now you can customize almost everything with columnUI, track info mod and single column... except for those two things (volume and seekbar) which look pretty ugly if you don't have a nice Visual Style.

There would be a way, if there was a command to seek to a certain point in a given song. As far as i know, foobar only has commands to seek relative to the current position -- for example, 'Playback/Seek ahead by 1 minute'.

Or you can go the wiki. I've made a couple of updates today, hopefully it is now up to date. And while you are there, you can also take a look for some informations that I would have missed.

Quote from: terrestrial on 2006-11-29 17:04:27

its in there... most stuff automatically gets added to both components since they share a lot of the same source code.

Does that mean buttons will be implemented into the single column playlist code?

As a side note, I'd just like to comment on terrestrial's awesome attitude towards bug reports and\or feature requests, as well as questions most developers find annoying (and i can understand those too, being one myself) like "when is the next version done".

It's nice to see such friendly and active developers in the community. Kudos

1. I've set the default font to Verdana 7pt, but whenever I try to use a larger amount of pt (like 20 pt on the second line below //Track in the codebox) that line get's drawn but the other lines don't  See the screenshots.

2. Whenever I enable "Update every second" using the code below, CPU usage goes up to 14% (P4 2.4GHZ). I don't use a lot of code, i suspect it has to do with my code for the $imageabs2 functions but i can't seem to solve the problem. Do variables on lines that have been commented out still get evaluated? Because commenting out the line with $puts and $alignabs doesn't seem to do much, makes up for a difference of 1 or 2%. With the "Update every second" CPU usages simply is 0%.

affects all the lines after.

buttons only work under "// PerTrack" (which is the default)

+ different redraw times for different sections.
   // Background
      // Put background stuff here (eg images). Only drawn once.
   // PerTrack
      // Put stuff that changes per track here (%album%, %artist%, etc.) Buttons go here as well.
   // PerSecond
      // Stuff that needs to update every second (%playback_time%, etc)

The stuff on top of the button is the overlay glass image,if i put it on //PerTrack mode,all other info is drawn over it and not beneath

So, for backwards compatibility we can just put a //PerSecond at the very beginning, and the other options are kinda just for resource management?

Another bug:when in //PerTrack mode some buttons response only once per track play.
I have a button that circles the playback modes,it only works once per track now.

I can't reproduce this... can you post a code snipped which shows this behavior?

$button2(72,21,0,0,13,12,,,
$if($stricmp(%cwb_playback_order%,'Shuffle (tracks)'),'Shuffle (albums)',
$if($stricmp(%cwb_playback_order%,'Shuffle (albums)'),'Shuffle (directories)',
'Shuffle (tracks)')),)
$alignabs(90,21,%_width%,%_height%,,)%cwb_playback_order%

I don't want to sound too critical but I do not like the idea of parsing comments as code. I don't like the idea of parsing rem statements in cue sheets for meta tags and I don't like using // comments in code to flag different sections.  Comments should be just that, comments. Perhaps there is a better approach to implementing these features, maybe a separate code box for each one? Maybe separate tabbed pages for each type in the config? I am hesitant to upgrade this component until all the button functionality is sorted out.