You are viewing a plain text version of this content. The canonical link for it is here.

Posted to fop-dev@xmlgraphics.apache.org by bu...@apache.org on 2002/02/07 15:21:06 UTC

DO NOT REPLY [Bug 6308] New: - retrieve-marker out-of page scope

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6308>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6308

retrieve-marker out-of page scope

           Summary: retrieve-marker out-of page scope
           Product: Fop
           Version: all
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: general
        AssignedTo: fop-dev@xml.apache.org
        ReportedBy: sfoucault@fr.ibm.com


The fo:retrieve-marker tag does not work if used with a boundary other 
than "page".

1- The first problem comes from the fact that StreamRenderer::getPreviousPage 
is based on the renderQueue member. But, StreamRenderer::queuePage method does 
not always fill the renderQueue vector (especially when there is no pending 
page reference).

2- The second problem comes from the fact that renderQueue stores 
RenderQueueEntry objects and StreamRenderer::getPreviousPage casts them to Page 
objects (Vector::elementAt and Vector::indexOf calls are wrong).

FYI : the same problem occurs in StreamRenderer::getNextPage

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org