Thread for help with the Shape meter

[sl23]

[jsmorley]

Code: Select all

[Rainmeter]
Update=1000
AccurateText=1
DynamicWindowSize=1

[Variables]

[StrokeStyle]
justMyStroke=Stroke Color 67,67,67,255

[MeterShape1]
Meter=Shape
Shape=Rectangle 4,4,300,150 | StrokeWidth 8 | Extend justMyStroke
MeterStyle=StrokeStyle
DynamicVariables=1
MouseOverAction=[!SetOption #CURRENTSECTION# justMyStroke "Stroke Color 67,67,67,0"][!UpdateMeter *][!Redraw]
MouseLeaveAction=[!SetOption #CURRENTSECTION# justMyStroke ""][!UpdateMeter *][!Redraw]

[MeterShape2]
Meter=Shape
Shape=Rectangle 4,4,300,150 | StrokeWidth 8 | Extend justMyStroke
MeterStyle=StrokeStyle
Y=10R
DynamicVariables=1
MouseOverAction=[!SetOption #CURRENTSECTION# justMyStroke "Stroke Color 67,67,67,0"][!UpdateMeter *][!Redraw]
MouseLeaveAction=[!SetOption #CURRENTSECTION# justMyStroke ""][!UpdateMeter *][!Redraw]

GIF.gif

[Yincognito]

I was thinking something like this, but it doesn't work:

Code: Select all

[sHighlight2]
MouseOverAction=[!SetVariable #CURRENTSECTION# sw "2"] [!UpdateMeter #CURRENTSECTION#] [!Redraw]
MouseLeaveAction=[!SetVariable #CURRENTSECTION# sw ""] [!UpdateMeter #CURRENTSECTION#] [!Redraw]
...

Jsmorley already provided a solution to your problem, but just so you know, you had an (unintentional?) mistake in the code above: it should have been [!SetVariable sw "2"] instead of [!SetVariable #CURRENTSECTION# sw "2"]. The latter form is used for the !SetOption bangs, not for the !SetVariable ones.

[sl23]

[balala]

Is it possible to use a similar instruction for the StrokeWidth?

Yep, it definitely is. For instance starting from jsmorley's above code, you have to add extenders for the Shape meters, then modify those ones:

Code: Select all

[Rainmeter]
Update=1000
AccurateText=1
DynamicWindowSize=1

[Variables]
StrokeAlpha=255
StrokeWidth=8

[sHighlight]
MouseOverAction=[!SetOption #CURRENTSECTION# MyModifiers2 "Stroke Color 47,47,47,0"][!UpdateMeter "#CURRENTSECTION#"][!Redraw]
MouseLeaveAction=[!SetOption #CURRENTSECTION# MyModifiers2 "Stroke Color 47,47,47,255"][!UpdateMeter "#CURRENTSECTION#"][!Redraw]

[MeterShape1]
Meter=Shape
MeterStyle=sHighlight
Shape=Rectangle 4,4,300,150 | Extend MyModifiers1, MyModifiers2
MyModifiers1=StrokeWidth #StrokeWidth#
MyModifiers2=Stroke Color 47,47,47,255

[MeterShape2]
Meter=Shape
MeterStyle=sHighlight
Y=10R
Shape=Rectangle 4,4,300,150 | Extend MyModifiers1, MyModifiers2
MyModifiers1=StrokeWidth #StrokeWidth#
MyModifiers2=Stroke Color 47,47,47,255

As you can see this time I modified the color of the stroke, through the MyModifiers2 option, previously added to both Shape meters.

[Yincognito]

I thought you had to use the Set Variable bang to use variables! So thanks for explaining

To make things clear: in general, the !SetVariable bang is indeed used to modify the value of variables, just like the !SetOption bang is used to modify options. So, from this point of view, you weren't mistaken - it was just a matter of confusing the former's syntax with the latter's in your original code.

In practice, you can use either of these two methods (or even a mixture of them) to do your thing - for example, jsmorley and balala used !SetOption bangs to make it happen, but you can easily use !SetVariable bangs if you like (the code below is based on balala's reply):

Code: Select all

[Rainmeter]
Update=1000
AccurateText=1
DynamicWindowSize=1

[Variables]
StrokeAlpha=255
StrokeWidth=8

[sHighlight]
MouseOverAction=[!SetVariable StrokeAlpha 0][!UpdateMeter "#CURRENTSECTION#"][!Redraw]
MouseLeaveAction=[!SetVariable StrokeAlpha 255][!UpdateMeter "#CURRENTSECTION#"][!Redraw]

[MeterShape1]
Meter=Shape
MeterStyle=sHighlight
Shape=Rectangle 4,4,300,150 | Extend MyModifiers1, MyModifiers2
MyModifiers1=StrokeWidth #StrokeWidth#
MyModifiers2=Stroke Color 47,47,47,#StrokeAlpha#
DynamicVariables=1
UpdateDivider=-1

[MeterShape2]
Meter=Shape
MeterStyle=sHighlight
Y=10R
Shape=Rectangle 4,4,300,150 | Extend MyModifiers1, MyModifiers2
MyModifiers1=StrokeWidth #StrokeWidth#
MyModifiers2=Stroke Color 47,47,47,#StrokeAlpha#
DynamicVariables=1
UpdateDivider=-1

Obviously, dynamic variables are required, and setting the update divider to -1 in order to update the relevant meters only when needed is a good idea.

Whether you prefer one method over the other, that's entirely up to you. I just wanted to point out that you can do it using !SetVariable bangs as well, in case you had the wrong impression on this...

EDIT: You can control the stroke width as well, by replacing, say, [!SetVariable StrokeAlpha 0] with [!SetVariable StrokeWidth 8] and [!SetVariable StrokeAlpha 255] with [!SetVariable StrokeWidth 1] in the above code (it makes more sense to me to make the highlighted/hovered frame thicker, instead of the opposite, by the way).

[sl23]

[balala]

Obviously, dynamic variables are required, and setting the update divider to -1 in order to update the relevant meters only when needed is a good idea.

No, it's not a good idea, it is absolutely needed! If you don1t set the UpdateDivider of both meters to -1, both will get receive the newly set transparency of the stroke. Using the !Setoption method, this can be avoided.

[sl23]

[Yincognito]

No, it's not a good idea, it is absolutely needed! If you don1t set the UpdateDivider of both meters to -1, both will get receive the newly set transparency of the stroke. Using the !Setoption method, this can be avoided.

I know - that's why I included them. Using "a good idea" instead of "absolutely needed" was just another way of saying it. I hate to always use the same words, so I was probably trying to be 'creative', LOL.

Other than that, there is no reason to avoid setting the update divider to -1 on the meters, as long as it doesn't interfere with other processes in the skin - after all, the 'highlight' is triggered on demand (i.e. on hover) anyway. Since the example was pretty basic, I didn't think it was a problem, but then, it always depends on what else you have in your skin.