Ah so you want a runable script then you will need the quotes if you are just going to execute the whole thing. I thought that you were looking to store data in a file. And Kees, I agree that if you are writting an XML then you have to have the quotes. Better to just use the dotNet object to write the XML for you so that you don’t have to do all the formatting your self though.
Yeah to start with I just want to export polygon objects to an executable maxscript with all the possibilities intact like all UV’s, vert colours, material ID’s etc… Then I’ll move onto modifiers and see if I can get my script to be able to write scripts to rebuild objects with stacks.
I didn’t read the whole thread…
But I did have to export XML code to a file from MaxScript, which required me to put quotes in a string.
So, in case you need String = “MyString” and export it exactly that way in a file, then you do
LongString = “String = “MyString” “
LongString += “<xml>id:“MyId”<\xml>”
Any ” is reading a ” string and not as a MaxScript quote.
Like that I managed to export a long Excel sheet in XML from a 3DMax scene, compiling a lot of stuff like polycount, vertex count, even texture weight in memory and doing automatic little nice Excel graph from MaxScript.
“system.xml” will get you every thing that you would need in reading and writting xml files without having to worry about quotes.
So far I found little to no example of a DotNet System.XML in MaxScript. Of course it works, but can’t find example script.
Aside, from this page : http://www.functionx.com/vcsharp/xml/Lesson06.htm it appears somehow problematic to return XML value between quotes. One of their example of subchild is to store the hole subchild group as a string… Which bring us back to our original problem of having quotes in a string.
Aside, I’m not sure which system is the fastest. Using system.xml or just parsing the xml you want… To me, it seams that both way would require almost the same ammount of script.
If the dotnet xml system is giving you problems, then perhaps consider writing your own XML classes/struct in maxscript.
That’s what I did, not too much work, and you’ve got full control.
Not really as you can get all elements as an array. You can create and set properties and don’t have to worry about double quotes as it will do it for you. You can get an element in a file and insert elements into it. As was suggested to me, if you use xml.write it is probably faster them xml.xmldocument how ever it isn’t as flexable I don’t think.
The code below will write out a new xml doc with properties for the objects in the scene. The xml doc is sorted by hierarchy and can be read that way.
dotnet.loadAssembly "system.xml.dll"
xml=dotNetObject "system.xml.xmlDocument"
showProperties root
showMethods root
root=xml.CreateElement "root"
xml.AppendChild root
fn sceneToXml obj root=
(
node=xml.CreateElement obj.name
node.SetAttribute "Object" obj.name
node.SetAttribute "wireColor" (obj.wireColor as string)
node.SetAttribute "transform" (obj.transform as string)
node.SetAttribute "classOf" ((classOf obj) as string)
root.AppendChild node
for x in obj.children do
(
sceneToXml x node
)
)
for x in objects do
(
if x.parent==undefined then
(
sceneToXml x root
)
)
xml.save "C:\ est.xml"
edit "C:\ est.xml"
Quite cool and quite useful. Thanks.
Gonna bookmark this page.
However, there is time where you can’t avoid the need of quotes… Like the XML header of a Excel files.
Very true, I wasn’t trying to say you didn’t need to.
Now writes out all modifiers and keys. Doesn’t handle tangents and other key settings how ever.
dotnet.loadAssembly "system.xml.dll"
xml=dotNetObject "system.xml.xmlDocument"
-- showProperties root
-- showMethods root
root=xml.CreateElement "root"
xml.AppendChild root
clearListener()
fn formatKeys keys root=
(
for k in keys do
(
node=xml.CreateElement "key"
node.SetAttribute "time" (k.time as string)
node.SetAttribute "value" (k.value as string)
root.AppendChild node
)
)
fn recurseNumSubs sub root=
(
node=xml.CreateElement "subAnim"
node.SetAttribute "name" sub.name
node.SetAttribute "classOf" ((classOf sub) as string)
node.SetAttribute "superClassOf" ((superClassOf sub) as string)
node.SetAttribute "value" (sub.value as string)
node.SetAttribute "index" (sub.index as string)
node.SetAttribute "isAnimated" (sub.controller.isAnimated as string)
node.SetAttribute "object" (sub.object as string)
if sub.controller!=undefined and sub.controller.keyable then
(
formatKeys sub.controller.keys node
)
root.AppendChild node
for i = 1 to sub.numsubs do
(
recurseNumSubs sub[i] node
)
)
fn formatModifiers mod root=
(
node=xml.CreateElement "Modifier"
node.SetAttribute "name" mod.name
node.SetAttribute "classOf" ((classOf mod) as string)
node.SetAttribute "superClassOf" ((superClassOf mod) as string)
root.AppendChild node
)
fn sceneToXml obj root=
(
node=xml.CreateElement "Object"
node.SetAttribute "Name" obj.name
node.SetAttribute "wireColor" (obj.wireColor as string)
node.SetAttribute "transform" (obj.transform as string)
node.SetAttribute "classOf" ((classOf obj.baseObject) as string)
node.SetAttribute "superClassOf" ((superClassOf obj.baseObject) as string)
node.SetAttribute "material" ((obj.material) as string)
for mod in obj.modifiers do
(
formatModifiers mod node
)
for i = 1 to obj.numsubs do
(
recurseNumSubs obj[i] node
)
root.AppendChild node
for x in obj.children do
(
sceneToXml x node
)
)
for x in objects do
(
if x.parent==undefined then
(
sceneToXml x root
)
)
xml.save "C:\ est.xml"
edit "C:\ est.xml"
Yeah, like that you could convert a whole scene with everything inside into XML.