Quote:
Originally Posted by Drumstix42
I have a feeling you can only set a property using a variable, but not navigate the XML tree with a variable.
|
I'm not entirely sure what you are trying to do, but your issue may be that you can always just resolve one variable per step. You are trying to do two in one.
The first step is to resolve your (name). Once you have that done, you can then resolve the XML path and address the visible parameter.
As an example an excerpt from my curing code which pulls the cure spell name from a file based on several variables. This is a three step process where I first "build" the correct location in the XML tree for the name, then create a script to pull the name into another variable and finally execute that script:
<Button Name="Configure"/>
<Button Name="GetSpellLocation" OnPress="SpellLocation='Parent.ProfitUI_Cures.' ## (Parent.Parent.Parent._HUD.ProfitUI_SubclassDetector.Subclass) ## '.' ## (Parent.CureName) ## 'Cure'
Parent.Configure.OnPress='Parent.Cure=' ## (SpellLocation)
Parent.Configure.Press=true"/>