These will include all options for "position", as well as the other options like "Draggable" and "StayOnScreen".
This does not include support for (which would not be logical at all), (which is not logical for a single skin), or or , which can already be defined at the skin level.
See Reference / Skins / [Rainmeter] Section / Default Settings in the documentation for details.
The very first time this skin is loaded, it will use the DefaultWindowX and DefaultWindowY values defined in the skin. Those values will be set and written in the [ConfigName] section of the skin in Rainmeter.ini. If the user of the skin moves the skin subsequent to that, the user's changes will be written and used from then on. In that sense, this is very much similar to a Layout, but without any external Layout file.
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...