Importing a layout on top of an old one / global layout settings

[Krainz]

Hi,

I'm developing a package of skins, and I'm conflicted between having one skin with dozens of meters or dozens of skins with only a few meters.

The design issue is: with a full-fledged skin, whenever the end user loads the skin into another layout profile, the X and Y positions of the elements (meters) are all set with no need to be configured.

However, with dozens of skins, the X and Y positions of those skins would only be determined in the layout configuration, so if the user loads a previous layout, or creates a new one, the UI elements (now skins) would be with incorrect X and Y positions.

What makes me choose between the two is that several skins apparently works more fluidly with Rainmeter as opposed to a unified skin with many many meters.

So, is there a way of loading a new layout on top of an old one? Like, if the user downloads my project and reverts to an old layout they had been using before, can they just double click something and "import" the X and Y positions of my skins so they don't get misplaced?

Or maybe saving that X and Y positioning information "globally" so the skins would be in the correct position no matter what layout the user loads or creates?

[balala]

So, is there a way of loading a new layout on top of an old one? Like, if the user downloads my project and reverts to an old layout they had been using before, can they just double click something and "import" the X and Y positions of my skins so they don't get misplaced?

Or maybe saving that X and Y positioning information "globally" so the skins would be in the correct position no matter what layout the user loads or creates?

No, unfortunately the answer to both questions is "no, there is not". When loading a layout, the old one is unloaded. Nor the skins, nor their position or settings are not kept. This is one of the purposes of layouts.

[Krainz]

Is there a way to write on the rainmeter.ini settings through a bang then?

This way, every time the skin is loaded, it would write the most optimal settings to rainmeter.ini and then reload all skins.

[balala]

Is there a way to write on the rainmeter.ini settings through a bang then?

Of course. Use the !WriteKeyValue bang. For instance the following bang writes to 0 (third parameter) the MyParameter option (second parameter of the bang) of the MyConfig section (first parameter) of Rainmeter.ini (last parameter): [!WriteKeyValue MyConfig MyParameter "0" "#SETTINGSPATH#Rainmeter.ini"].

[Krainz]

Thanks balala!

A final question, on the matter of writing a keyvariable to rainmeter.ini every time the skin is loaded, would it visibly affect performance?

[balala]

A final question, on the matter of writing a keyvariable to rainmeter.ini every time the skin is loaded, would it visibly affect performance?

I'm not sure. You have to try it out.

[qwerky]

Is there a way to write on the rainmeter.ini settings through a bang then?

This way, every time the skin is loaded, it would write the most optimal settings to rainmeter.ini and then reload all skins.

Be sure not to create an endless loop...