Check out the technotes at MACR.
I think it has a memory leak, I think it may crash otherwise, and basically
MACR says well, use the Flash one.
roymeo
At 08:18 AM 7/29/2003 -0400, you wrote:
Thanks, Mathew.
after hearing some of the issues people had with it and remaining bugs
that are not
Check out the technotes at MACR.
I think it has a memory leak, I think it may crash otherwise,
and basically MACR says well, use the Flash one.
No, not quite. To start, yes, there is a memory leak in the XML parser Xtra that's
documented in a tech note:
http://www.macromedia.com/go/16805
Thanks for addressing the issue, Tom.
Pardon my naiveté, but to what extent is the memory leak an issue? I am developing a
learning tool that parses XML. Depending on how far into this DVD-ROM they get, the
XML could get lengthier and lengthier, but I'd say not more than 10-20k of text.
Nice observation, Troy! Thanks!! I really do dig that object
inspector.
- Michael M.
When debugging, is there any way to see the structure of parsed xml
under the variable tabs (DMX interface). Currently, all I see there
is the instance of the xtra: Xtra child XmlParser 2 2c1bfe0.
Thanks, Mathew.
after hearing some of the issues people had with it and remaining bugs
that are not fixed.
So, what are some of the remaining bugs and issues with Macromedia's xml
parser xtra?
- Michael M.
[To remove yourself from this list, or to change to digest mode, go to
Try using Andy White's XML Parser scripts... Organizes everything nice
and neat for ya... Even provides search functions...
http://www.shocknet.org.uk/defpage.asp?pageID=90
If you like the way flash does it (and if you find out it is more
efficient), you can always use global flash objects in
On Monday, July 28, 2003, at 03:07 PM, Mendelsohn, Michael wrote:
When debugging, is there any way to see the structure of parsed xml
under the variable tabs (DMX interface). Currently, all I see there is
the instance of the xtra: Xtra child XmlParser 2 2c1bfe0. I'd like
to be able to see a
