If an expression reference another expression in a parent fo, the parent
fo expression must be evaluated against the LayoutContext that was in
effect for the parent fo and *not* against the child fo LayoutContext.
fo:block id=a border-start-width=10%
fo:block id=b border-start-width=inherit
[Peter B. West]
Finn,
When I apply your most recent patch (10366) against a cvs updated HEAD
tree and attempt to compile, I get the following:
[javac]
/usr/local/src/fop-HEAD-finn/src/java/org/apache/fop/fo/properties/LinearCombinationLength.java:60:
After applying the patch (10366), the
On Sat, Feb 21, 2004 at 12:24:24PM +0100, Finn Bock wrote:
Question: What to do if I insert a fo:wrapper between fo:flow and
fo:block? That makes it the parent of fo:block, but it has no layout
manager corresponding to it. Override getLayoutDimension on it?
I don't think so, but perhaps I
Andreas L. Delmelle wrote:
-Original Message-
From: Peter B. West [mailto:[EMAIL PROTECTED]
Thanks Andreas. Yes, I disagree, but then, so does the spec. What
information *should* do is not terribly relevant. We need to work out
and express what information *must* do to get this
Finn Bock wrote:
[Peter B. West]
Finn,
When I apply your most recent patch (10366) against a cvs updated HEAD
tree and attempt to compile, I get the following:
[javac]
/usr/local/src/fop-HEAD-finn/src/java/org/apache/fop/fo/properties/LinearCombinationLength.java:60:
After applying the
Finn,
Nice. The parser, of course, looks after all of the expression-ordering
questions for you, and you have only to collect the unresolved items.
I'll adopt this for alt-design.
Peter
Finn Bock wrote:
[Peter B. West]
Can you describe your expression tree in more detail?
The line above
