The caveat of the !Move, and now !SetOption, families is that they only allow a single destination to be specified. For shifting, there's #CURRENTCONFIGX/Y# and section variables, but for a bunch of objects with various and unknown X/Y values...
Code: Select all
[!SetOption Meter1 X ([Meter1:X]+80)][!SetOption Meter2 X ([Meter2:X]+80)][!SetOption Meter3 X ([Meter3:X]+80)]...
Code: Select all
!ShiftMeterGroup SomeGroup 80 0
#CURRENTCONFIGZPOS#
Since ZPos isn't binary, toggling between 2 states is a little challenging. The most difficult part is respecting the current user setting so the toggle isn't wasted setting the wrong setting. It's possible to retrieve the value from Rainmeter.ini with regex, but messy. I'll probably end up writing that lua function anyway, but I'm just throwing this one out there. Or how about
RAINMETER:GetSection('ExampleSkin')
exampleSkin:GetValue('AlwaysOnTop')
(For configuration skins that need to configure other skins)
or
SKIN:GetSetting('AlwaysOnTop')
BlurRegion
I'm using either execute-once measures or lua to utilize section variables in blur regions, so the first arbitrary blur region required for blur to function just seems a little silly.
Code: Select all
[Rainmeter]
Blur=1
BlurRegion=1,0,0,1,1 <-silly