QUOTE (flattspott @ Feb 28 2004, 10:24 PM) |
I see the stuff in the ActionScriptReadMe.txt but it's got me confused. LoadDialogFromXML <UIHandle> <XMLHandle> <XMLLocation>
Now would this be how it works if you had multiple dialogs in one XML file?
XMLOpen ScriptXML $ActualPath$\Scripts\SomeScript\SomeScript.xml LoadDialogFromXML FirstDLG ScriptXML !.FirstDialogToLoad LoadDialogFromXML SecongDLG ScriptXML !.SecondDialogToLoad
Is the XMLHandle like a Variable of sorts for the main script\dialog xml file location? That way you don't have to keep specifying the file location whenever you want to create a dialog? And does this mean that if you use XMLClose then your dialog will mess up (Like you can't GET or SET values)? |
The example you types in is exactly how it's used.
You open an XML object, then create new Dialog UI Objects from nodes within the XML.
Alternatively, you might have:
CODE |
XMLOpen ScriptXML $ActualPath$\Scripts\SomeScript\SomeScript.xml LoadDialogFromXML FirstDLG ScriptXML !.Dialogs.Dialog?DlgID=IPSetupOne LoadDialogFromXML SecongDLG ScriptXML !.Dialogs.Dialog?DlgID=IPSetupTwo
|
to take advantage of the new query locational method.
...and yes, you should keep the XML object around for the life of the dialogs, unless it's an internal XML node.