Hi,
Thanks for the bump
Please find attached the sample ( published with U4.3.4)
I store the xml in a text file and use a proxy to reference that asset.
then I use the action only
XmlSelectSingleNode
The actual xpath query is:
//layer[@name='H_2_Poppy']
but since you likely want the name to be dynamic and hosted in an fsm variable, you change it to:
//layer[@name='_0_']
and add a variable associated to the xpath query. Check the "XmlSelectSingleNode" in the demo to see how the xpath si then parsed using the variable values
this XmlSelectSingleNode action can in one go also retrieve properties of the found node ( only if found obviously), and the last part of the action gets the various informations you need, notice the automatic conversion of variable tapes, since in xml everything is a string, you can still however store values inside any fsm variable, the conversion will be done automatically or warn if impossible.
The "Store Reference" property of the action is simply a way to save in memory the found node so that later in the game, ANYWHERE in your scenes on any fsm, you can query again that node simply by reference the value of "Store Reference".
hopefully, that will explains the process clearly, search the web for tutorials on xml xpath and experiment online, you'll find numerous xpath testers to validate your queries quickly. However, the context is slightly different in XmlMaker so it's usefull also to check out the various examples to really get a feeling of the most used types of xpath queries.
Bye,
Jean