if you happen to have Flash 2004 then reads its dos on the Flash components especially with respect to methods etc.. I think much of the Flash documentation is also available for download from the Flash support site as well but I could be wrong.
There was a lot of documentation to write and rewrite for this release so some things will have gotten missed. But to answer your question on xml:
1). Flash Components require Flash Objects to be passed in as parameters, NOT lingo objects. There is no autoconversion of Lingo object types to Flash object types except for numbers, strings and booleans and perhaps void.
2). If your passing in a Flash Object to any Flash component and/or swf file, IT MUST BE MADE BY THE SWF OR COMPONENT that you are passing it in to. In Dir MX, you could sometimes get away with creating a global flash object and then passing it into a swf but that door has been slammed shut in Director MX 2004. It was bad practise to begin with and often could lead to eratic and unexpected behavior especially if scope changed etc..
foXML = sprite("myTree").newObject("XML")
foXML.ignoreWhite = true
foXML.parseXML(member("XML").text)
sprite("myTree").dataProvider = foXMLin theory the above should work.
Does that help to alleviate any of your fustratations...
also maybe check out the Director DevNet center on Macromedia's website, it might have some useful information that will explain things a bit.
Sincerely Mark R. Jonkman
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus&pgmarket=en-ca&RU=http%3a%2f%2fjoin.msn.com%2f%3fpage%3dmisc%2fspecialoffers%26pgmarket%3den-ca
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
