He only has to open the skin code to edit it, not to see it, since it's right there on the right part of the Skins tab from Manage Rainmeter, if you selected the corresponding .ini file from the left side. But yeah, I also think it's hard to follow, especially for many nested folders in a suite, where you'd have to click all the way to the desired .ini file. Another disadvantage that I didn't thought when writing it earlier is that you'd have to repackage the skin installer to have the contents of that option "saved" in the skin package - this one is a much bigger disadvantage, since you'd have to add the necessary plugins (x86 and x64), layouts and all that when repacking. Yuck, not a good choice indeed!The disadvantage of this approach is that is hard to follow. User has to open the skins code in order to see this information. Approachable, but not too convenient, in my opinion.
So that leaves us with the rudimentar .txt choice and renaming, as some of the simplest and most "neutral" ones, unless you have other ideas...
Statistics: Posted by Yincognito — Yesterday, 8:32 pm