RE: [flexcoders] Filtering descendant XML nodes based on multiple tag names

I tried that but with no success. If I do: topElement.descendants().(hasOwnProperty(@id)); Then I get a long XMLList. But if I do: topElement.descendants().(hasOwnProperty(localName)); Then I get an empty XMLList. I looked at the ECMA spec and they talk about accessing any property using

RE: [flexcoders] Filtering descendant XML nodes based on multiple tag names

Thanks very much - works perfectly. Tracy Spratt wrote: Almost all properties ain e4x are implemented as methods. So you want localName(). Try: topElement.descendants.(localName() ==X || localName() == Y) ; Tracy -- View this message in context:

RE: [flexcoders] Filtering descendant XML nodes based on multiple tag names

Have you tried topElement.descendants().(localName ==X || localName == Y) ? Not able to check the exact syntax on that just now (is localName an attribute???) , but I think that's worked for me before. There was a post yesterday that seemed to be concerned with a similar sort of thing, you may

RE: [flexcoders] Filtering descendant XML nodes based on multiple tag names

, April 18, 2008 8:31 AM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Filtering descendant XML nodes based on multiple tag names Have you tried topElement.descendants().(localName ==X || localName == Y) ? Not able to check the exact syntax on that just now (is localName an attribute

RE: [flexcoders] Filtering descendant XML nodes based on multiple tag names

: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Tracy Spratt Sent: Friday, April 18, 2008 2:18 PM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Filtering descendant XML nodes based on multiple tag names Almost all properties ain e4x are implemented as methods. So you