It is currently June 20th, 2019, 6:00 pm

Updating your skins with .rmskin Advanced options

Our most popular Tips and Tricks from the Rainmeter Team and others
User avatar
jsmorley
Developer
Posts: 19266
Joined: April 19th, 2009, 11:02 pm
Location: Fort Hunt, Virginia, USA

Updating your skins with .rmskin Advanced options

jsmorley » September 13th, 2013, 11:51 pm

There are advanced options in the tool for creating a .rmskin of your skin or suite of skins that can help with distributing updates and new versions of your work.

Advanced .rmskin Options
User avatar
SHADODESIGN
Posts: 4
Joined: December 18th, 2013, 2:10 pm

Re: Updating your skins with .rmskin Advanced options

SHADODESIGN » March 25th, 2015, 6:52 am

yeh you need to add a way to bring together parts of folders or existing skins into a new folder to make a new skin in a completely new folder! once all parts are highlighted or selected and add one by one! Other skin programs have this. but this has more to offer so this might be something to think about! 8-)

as at the my skin only works from each folder when I try and bring it together the centre piece goes black and white! and I can't work out why?
LIVE FAST DIE YOUNG AND TAKE EVERY DAY AS A NEW ONE!

BECAUSE YOU DON'T KNOW WHAT IS GOING TO HAPPEN!

WHEN YOU TURN THAT NEXT CORNER!!
User avatar
jsmorley
Developer
Posts: 19266
Joined: April 19th, 2009, 11:02 pm
Location: Fort Hunt, Virginia, USA

Re: Updating your skins with .rmskin Advanced options

jsmorley » March 25th, 2015, 1:21 pm

SHADODESIGN wrote:yeh you need to add a way to bring together parts of folders or existing skins into a new folder to make a new skin in a completely new folder! once all parts are highlighted or selected and add one by one! Other skin programs have this. but this has more to offer so this might be something to think about! 8-)

as at the my skin only works from each folder when I try and bring it together the centre piece goes black and white! and I can't work out why?
We are not going to do anything along these lines.

There are just way too many ambiguous complexities with building a process that allows you to select skins from various "root level" folders and create a single .rmskin that installs them all.

First, a decision must be made about what that means. When the .rmskin is installed are the skins installed to the original root level folders, or it the intent to create a single new root level folder and install all the skins as sub-folder under that.

If it is the former, we would never support that. We are not going to help authors to overwrite existing skins by other authors on a user's system. That can only lead to problems with users who don't understand that they are putting their current setup at risk when they install your .rmskin to try it out.

If it is the later, there is just no way to make that reliable. The way the @Resources folder works in Rainmeter is that it must be at the "root level" folder of the skin using stuff in it, and many of the skins you might "select" will have their own @Resource folders and references to it in the skins, and those will stop working. The only solution would be to somehow "merge" all existing @Resource folders into one, and put it in the new root level folder. We would never do that, as the risk of duplicate file names like "Variables.inc" or any number of other files and folders is just too great. This is certain to just blow up and cause problems.

To be honest, we are not really huge fans of folks who just take a dozen skins from other authors, stick a wallpaper behind it and release it as their own. That being said, as long as the authors have used a licence that allows it (most do) and proper credit to the original authors is given, then so be it.

However, it is up to YOU to do the up front work required to create a compilation of skins, at a single root level folder location, and resolve any issues with @Resources or other references to external files used by the various skins. Once you have the new setup created and tested, and you are sure that everything works as it should in the new location, then just create your .rmskin.

What is installed by your .rmskin will be in "your" root level folder location, will not replace or break existing skins the user may have, and will have been tested and tweaked as needed by you to ensure it works correctly.

That is how it is going to stay.