%St(x,y,w,h,<bar params>,setting,<setting name as it appears in config.cfg>)
Here's an example using balance:
%St(0,0,-,-,GENERIC_BAR,backdrop,GENERIC_BAR_BACKDROP,slider,SCRUBBER_HANDLE,setting,balance)
Note that the sections in CAPS are all image identifiers preloaded at an earlier stage.
Also, please note, that purely from a function and design standpoint, this is potentially a pretty horrible idea.
This will sacrifice a major portion on the available real estate of the wps/sbs for the sake of duplicated functionality, and unless your theme is touchscreen enabled, you can't actually do anything practical with these bars, and even if it is touchscreen enabled, at present, this won't function as expected (it will manipulate the config parameter but never actually save the config, and as such, never apply the setting) unless you compile your own build containing these
pending patches.
The basic gist of what I'm saying is that to me this seems pretty impractical unless the device is touch enabled, making these bars: a - useful, and b - allowing the screen view to be toggled on demand so that there isn't a massive area of screen real estate wasted presenting information that will be static 99% of the time.
If the device is touchscreen, you can easily toggle this view conditionally, but with a non-touch target, you would be limited to either displaying this full-time (which is incredibly wasteful as this real estate could be used to display much more relevant data), or toggle it via one of the hardware or state sensitive conditions.
I note that you said that this made the theme "too big", and that concerns me somewhat, that tells me that you have either a low resolution device, a low memory device, or potentially both. And if you're getting to a point that a few bytes of theme code makes a difference, this means you've reduced the audio buffer to near non-existence, which will screw you on efficiency and battery life down the track due to having to pretty much constantly refresh the now tiny buffer. This is an audio player, primarily, having it look sexy isn't too appealing if a side effect of that is that you'll be unable to play audio.
If you want to have a look at how these bars work, and/or examine other instances of syntax usage, you can have a look at the bones of a project I have been working on for the past...forever,
here.
[Saint]
Rockbox Technical Forums
Topic: Equalizer in WPS Screen (Read 2090 times)