Presumably if you "know" that the name of your config and skin are Feedreader and FeedReader.ini, you also "know" the name of the root config, and so this has really limited practical value in most cases. However I could see a use for it if for instance you have a "production" and "development" version of a suite that you have in different root config folders, and want to have a generic way to do that !ActivateConfig bang.thatsIch wrote:
Finally [!ActivateConfig "#ROOTCONFIG#\Feedreader" "Feedreader.ini"] from another skin of your suite. Nice!
It is currently April 20th, 2024, 5:23 am
Paths and Configs
-
- Developer
- Posts: 22629
- Joined: April 19th, 2009, 11:02 pm
- Location: Fort Hunt, Virginia, USA
Re: Paths and Configs
-
- Posts: 446
- Joined: August 7th, 2012, 9:18 pm
Re: Paths and Configs
Actually not in all cases. Presumably you send your skin around in a *.rmskin but for example in GitHub you download it as X-master zips and you end extracting them and putting them directly as that in your skin path folder. Now you don't need to change the RootConfig Name (removing the -master from the folder)
Powered by Sublime Text 3 with Rainmeter-Package