yeah, typo (copied code without changing the names to make any sense in the context of this post).
If that code is working, I may have a more subtle bug working somewhere...I'm going to guess that it may be from running a filter and setting the XMLList directly to an XML object -- Either way, somehow the link to the parent XML document is being stripped between calls to nextPage(). Thanks for the confirmation. I'll post back if I learn anything new (unless I have a really stupid typo or some such nonsense). On Wed, Apr 16, 2008 at 1:46 PM, Peter Hall <[EMAIL PROTECTED]> wrote: > When porting from AS2, you might find it more direct to use > XMLDocument instead of XML. This behaves exactly like the AS2 XML > object. > > Having said that, I tried your code and it seemed to work (I assumed > where you put node.childIndex() it was a typo and you meant to write > _currentPage.childIndex()). > > > Peter > > > > > On Wed, Apr 16, 2008 at 7:41 PM, Jer Brand <[EMAIL PROTECTED]> wrote: > > I'm in the process of switching some of my apps over to AS3, with one > class > > used to access and XML object giving me a fits. > > > > The class is used to navigate through a serious of pages, with the XML > > acting like the table of contents (chapter/topic/page). Applications > using > > this class would make calls like myClass.nextPage() and be given the > > location of the swf to load, as well as other metadata about that page. > > > > Simple enough in AS2. When the XML loads, I grab a reference to the > first > > page in the book and store it in a class variable (psudo code): > > > > _currentPage = _toc.firstChild.firstChild.firstChild ; > > > > and then subsequent calls to nextPage would use: > > > > _currentPage =_currentPage.nextSibling ; > > return _currentPage ; > > > > > > The code itself seems simple to port to AS3, however, I'm not getting > the > > results I'm expecting: > > > > _currentPage = _toc.chapter[0].topic[0].page[0] ; > > > > works fine however > > > > _currentPage > =_currentPage.parent().children()[node.childIndex() > > + 1]; > > return _currentPage ; > > > > > > causes an error. The failure appears to be _currentPage.parent() as > this is > > returning null. > > > > So after that long winded description, my fear/guess at this point is > that > > the XML object _currentPage when set by > _toc.chapter[0].topic[0].page[0] > > is creating an *isolated XML fragment* with no connection to the parent > XML > > object. This differs from how I was working in AS2, where the XMLNode > > "_currentPage" behaved like a pointer to the position of the node > within the > > XML object. > > > > Is this assumption correct? If so, know any way of getting around it? > > Would using _currentPage as an XMLNode solve the problem, and if so, is > it > > possible to perform E4X filters/searches on an XMLNode or is it back to > > XPath for AS3? > > > > Jer > > _______________________________________________ > > Flashcoders mailing list > > Flashcoders@chattyfig.figleaf.com > > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > _______________________________________________ > Flashcoders mailing list > Flashcoders@chattyfig.figleaf.com > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
