Hi Matt, No, afraid not.. I actually use the select1 variable elsewhere, so it's not just that trace which is the problem.
Thanks for the suggestion though! 2009/4/17 Matt S. <[email protected]> > Does it make a difference if you write the trace as : > > trace("formData="+formData); > trace("select1:"+ select1); > > > On 4/17/09, Tim Hawkins <[email protected]> wrote: > > Hi, > > I've come across this a few times in my own code, but haven't seen it > > mentioned online - though it's a difficult thing to google for. > > > > In the following function, if the trace at the top is present, formData > > traces a load of XML and select1 also traces a load of XML. > > > > If I comment out the top trace, formData still traces the same pile of > XML > > but select1 traces null! > > > > public function testMakeModelFilterWorks():void { > > > > trace(""); > > default xml namespace = NAMESPACE; > > > > var select1:XML = formData..select1[2]; > > trace("formData=", formData); > > trace("select1:", select1); > > > > // etc > > default xml namespace = null; > > } > > > > Any ideas? I'm getting fed up of leaving 'trace("");//don't delete me' at > > the top of functions. > > (I don't think it's a timing thing, if I put a 100000-item > > increment-a-variable loop in there instead of a trace the E4X still > fails.) > > > > t. > > _______________________________________________ > > Flashcoders mailing list > > [email protected] > > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
