|
From: Tom D. <tom...@gm...> - 2014-09-29 00:18:55
|
Please disregard. This turned out to be a bug with the complex way I was using VTD, rather than a bug with VTD itself. Tom Deering | PhD Student | ISU ECpE Software Systems | (563) 249-9277 On Fri, Sep 26, 2014 at 8:22 PM, Tom Deering <tom...@gm...> wrote: > Specifically, I am trying to traverse the element tree recursively. I'm > wondering if coming back to the parent causes the VTDNav to lose track of > what the next sibling should be? > > RecursiveProcessing(n): > go to first child > for child c > RecursiveProcessing(c) > go to next sibling > go to parent > > Tom Deering | PhD Student | ISU ECpE Software Systems | (563) 249-9277 > > On Fri, Sep 26, 2014 at 6:40 PM, Tom Deering <tom...@gm...> > wrote: > >> I noticed that, at least for my documents, moving the VTDNav to the >> NEXT_SIBLING or LAST_SIBLING does not work. Even for documents where the >> elements have many siblings, this method always returns false. Other moves >> such as PARENT and FIRST_CHILD seem to work. >> >> Thoughts as to why moving to siblings does not work? >> >> Tom Deering | PhD Student | ISU ECpE Software Systems | (563) 249-9277 >> > > |