View Full Version : Extension Priority
unerwünscht
March 31st, 2011, 00:01
Any chance of getting an extension priority setting? Example, You load a Skin Ext. and my new Portrait Frames ext. Since both extensions change the same files you get unpredictable results in the end. It would be nice if we could have a load priority, so we could tell it to load the skin first and then the frame extension.
Zeus
March 31st, 2011, 01:05
I'll second the request. It would be a useful feature.
Or the ability to define an extension type and force the priority of extensions by type. e.g.
- new functionality then
- custom rules then
- skins
- component graphics
Also, I wonder if making extensions dependencies would work e.g.
- skin extension depends upon ruleset
- frames extension depends upon ruleset and skin extension
Downside of course is its not generic i.e. you have to name the extension dependancies explicitly.
saithan
March 31st, 2011, 04:16
i do not know if this is what you meant doc.
but currently i been using this with my personal skin and it seems to work
<properties>
<name>Valahn Theme</name>
<version>1</version>
<author>Fantasy Grounds Gurps Ruleset</author>
<description>Gurps 4e ruleset theme extension</description>
<ruleset>
<name>GURPS_4e</name>
</ruleset>
<ruleset>
<name>GURPS_4e</name>
</ruleset>
<dependency>
<name>GURPS_4Enhanced</name>
<minversion>0.56</minversion>
<maxversion>0.56</maxversion>
</dependency>
</properties>
the skin ext will show a red X if enahanced it not loaded or if the version of enhanced it higher than the minversion.
Zeus
March 31st, 2011, 07:51
saithan - pretty much, yes.
I am thinking if you chain the extensions via dependencies it may force the load order of the extensions to a particular order.
Powered by vBulletin® Version 4.2.1 Copyright © 2024 vBulletin Solutions, Inc. All rights reserved.