RFC: Extend skin engine to handle EQ settings

EQ settings are actually an array of 3 ints.  I added a skin parameter
token that allows specifying which array element to use.

So instead of this now-incorrect syntax:

   %St(0,0,-,-,image,eqbar.bmp,vertical,setting,eq band 1 gain)

You would use:

   %St(0,0,-,-,image,eqbar.bmp,vertical,soffset,2,setting,eq peak filter 1)

(the 'gain' is the third element in the eq setting array, thus soffset 2)

Change-Id: Ibda712ab87759efb45420566c967742bcefb513b

1 files changed, 2 insertions, 1 deletions

diff --git a/manual/appendix/wps_tags.tex b/manual/appendix/wps_tags.tex
index 70fef71015..94b61e9534 100644
--- a/manual/appendix/wps_tags.tex
+++ b/manual/appendix/wps_tags.tex
@@ -85,7 +85,7 @@ show the information for the next song to be played.
 
     \config{\%Vi('label',\dots)} &
     Declare a Custom UI Viewport. The `\dots' parameters use the same logic as
-    the \config{\%V} tag explained above. See section \ref{ref:Viewports}.\\ 
+    the \config{\%V} tag explained above. See section \ref{ref:Viewports}.\\
 
     \config{\%VI('label')} & Set the Info Viewport to use the viewport called
     label, as declared with the previous tag.\\
@@ -708,6 +708,7 @@ display cycling round the defined sublines. See
     \opt{touchscreen}{
         \item[notouch] -- don't create the touchregion for progress/volume bars.
     }
+  \item[soffset] -- For compound settings (such as the equalizer), this lets you pick which element in the set to use. The next param must be the number.  Must be specified prior to the setting name.
   \item[setting] -- Specify the setting name to draw the bar from (bar must be
     \%St type), the next param is the settings config name.
 \end{description}