Problem Solved:
Authors wishing to create thier own style and location buttons, for custom profiles, previously would need to modify the Preset Parser program, which generates the XML document for each button. (Which requires source code, and Visual Basic programming know-how)
The only alternative was to use the CustomPreset buttons, and styles as they are. Which doen't fit into many of the really nice complete UI sets available.
Method For Creating your Own Custom Preset Buttons, and Styles, and putting them wherever you want.
I messed around with this on my girlfriends computer this morning, and came up with this as an example.
A single PresetParser can be created that will work for everyone.
So that you don't have to have different settings for each UI Author who wants to incorporate the buttons into thier UI.
This method will also work with the Preset Parser as it is now.
It's pretty easy to understand when you take a look at it.
The Mod Author would need to include these lines in he page that contains their own buttons.
Other than that, you are free to make your own buttons look, or act any way you perfer, including locating them anywhere within that page element. As long as they code them to set the appropriate custompreset checkbox.
<include>eq2ui_custompreset1.xml</include>
<include>eq2ui_custompreset1.xml</include>
<include>eq2ui_custompreset2.xml</include>
<include>eq2ui_custompreset2.xml</include>
<include>eq2ui_custompreset3.xml</include>
<include>eq2ui_custompreset3.xml</include>
Quote:
OnSet="Parent.Custom1.checked=true Parent.Custom1.checked=true Parent.Custom2.checked=false Parent.Custom2.checked=false Parent.Custom3.checked=false Parent.Custom3.checked=false Parent.ModAuthorsCustom2.checked=false Parent.ModAuthorsCustom2.checked=false Parent.ModAuthorsCustom3.checked=false Parent.ModAUthorsCustom3.checked=false r_performance=1.0 r_performance=1.0"
OnUnset="Parent.Custom1.checked=false Parent.Custom1.checked=false"
|
If this method is accepted by you guys, the next version of the preset parser can be simplified to create only one style of hidden buttons.
Making things a bit simplier for the end user, and giving Mod Authors much more freedom of placement and style of thier own buttons.
Untill Then, you can just modify 'Visible' control of the files, after the parser spits them out.
Maybe, now performance panel functions will find a way into Fetish!