Just to make sure I understand things correctly, the element list
construction needs to be seperated from the line breaking algorithm ONLY
when using it for auto table layout ? I am asking this because the
LineLayoutManager is not used exclusively by the TableLayoutManager, right ?
If this is correct, how do you recommend I do this split ? Should I
create a new "LineLayoutManager" ? Or should I actually change the
LineLayoutManger and reflect the change anywhere it is necessary in the
Jeremias Maerki wrote:
Here are my notes on AutoTableLayout I collected last year in case you
haven't seen them, yet. One of the more important parts will be to split
up the element list construction and the line breaking in
LineLayoutManager, because you can't do the line breaking as long as you
don't know the available IPD.
On 18.07.2006 21:30:39 Patrick Paul wrote:
Great this is exactly what I needed, just didn't know where to look
(just as I received your message I had coded my own little routine).
Now I need a little pointer on how best to fly over table rows without
"touching" them. I have some idea but I would prefer to check with the
Andreas L Delmelle wrote:
On Jul 18, 2006, at 20:46, Patrick Paul wrote:
Depends on what you mean by 'length': if you mean content-length,
have a look at layoutmgr.ElementListUtils.calcContentLength().
I've been "playing" a little with the TableLayoutManager code.
If someone would be kind enough to point me in the right direction
on how to determine the full length of each element list, it would
help a great deal.
If you mean number of elements --but you don't, do you? ;)