I think it should be relatively simple to rearrange PSLM to set up the
right page before the call to getNextBreakPoss(). What I'm wondering,
though, is why the breaks are handled during getParentArea using
information in Traits on areas and not through BreakPoss instances
during getNextBreakPoss() stage. Does anyone know? There are no such
traits described in the spec that I could find in a quick fly-over. And
IMO it doesn't make sense to do it this way. What am I missing?

On 10.02.2005 14:28:45 Jeremias Maerki wrote:
> Ouch! The PageSequenceLayoutManager has a big problem. It sets the
> reference IPD for the flow once at the beginning and then no more.
> Subsequent pages get their (correct) page master only during addArea
> stage through getParentArea(). But the flow reference area has to be set
> prior to doing any getNextBreakPoss() on a new page. So it's not
> resetPosition() methods that don't behave as I claimed in my earlier CVS
> message (although I found a few strange things with resetPosition() while
> looking at table headers/footers).
> On 10.02.2005 13:52:35 jeremias wrote:
> > jeremias    2005/02/10 04:52:35
> > 
> >   Modified:    test/layoutengine/testcases normal-breaking4.xml
> >   Log:
> >   Adding an additional block at the end to see if a new block would behave 
> > differently.

Jeremias Maerki

Reply via email to