I would caution against overusing [Variables] when you don't really need them. You can make things more complicated than they really have to be.
Code: Select all
Text=Counter is: %1
LeftMouseUpAction=[!EnableMeasure ClickCounter][!UpdateMeasure ClickCounter][!UpdateMeter ShowClicks][!Redraw]
So we start with ClickCounter disabled. It will be "0". Then when we click, we enable the measure and update it one time so it changes to "1". Since we have UpdateDivider=-1 on the measure, it won't keep counting, but will update only once and stop at "1". Then when you click again, the !EnableMeasure will be ignored as it is already enabled, and it will be updated once again to "2" and stop.
We then just bind the meter to the [ClickCounter] measure, and use that value in the Text option. There is really just no need for the extra step of passing the value through as a [Variable].
P.S. In 99.9% of cases you are going to really want LeftMouseUpAction instead of LeftMouseDownAction. Reacting to the "down" press of the mouse button will mean you can no longer drag the skin unless you hold down CTRL while doing it, and unless you want distinct actions on the down and up of the mouse button, for instance to simulate button image changing behavior on "over / down / up", LeftMouseUpAction is going to be a better choice.
You do not have the required permissions to view the files attached to this post.