These will include all options for "position", as well as the other options like "Draggable" and "StayOnScreen".
This does not include support for Active (which would not be logical at all), LoadOrder (which is not logical for a single skin), or Group or DragGroup, which can already be defined at the skin level.
See Reference / Skins / [Rainmeter] Section / Default Settings in the documentation for details.
Code: Select all
[Rainmeter]
Update=1000
DynamicWindowSize=1
AccurateText=1
DefaultWindowX=2020
DefaultWindowY=100
[Variables]
[MeterBack]
Meter=Shape
Shape=Rectangle 0.5,0.5,300,100 | StrokeWidth 1 | Stroke Color 150,150,150,255 | Fill Color 47,47,47,255
[MeterPosition]
Meter=String
X=151
Y=51
StringAlign=CenterCenter
FontSize=20
FontWeight=400
FontColor=255,255,255,255
SolidColor=47,47,47,255
Padding=5,5,5,5
AntiAlias=1
DynamicVariables=1
Text=X:#CURRENTCONFIGX# | Y:#CURRENTCONFIGY#
Probably the biggest advantage is the ability to distribute a skin, forcing some starting position and other settings, while not replacing all of the user's loaded skins with yours, which would be the result of using a Layout. Much of this can be done today with various skin !bangs used in OnRefreshAction in [Rainmeter], but it can be pretty complicated and geeky to force this to only be done once, when the skin is loaded for the first time, and not on subsequent refresh and reload. In general, don't "force" your desires on an end-user without good reason. Once they load your skin, it's theirs, not yours...