-----BEGIN PGP SIGNED MESSAGE-----
On Aug 23, 2005, at 22:09, Finn Bock wrote:
Andreas L Delmelle wrote:
The type should be a number with added 'force' enum. The number
property will then coerce a 'force' value into an EnumNumber which is
a number that also holds a enum value, but only the property subsystem
needs to know that.
(Just the man whose input I was looking for :-) )
OK, thanks for clarifying.
* Another issue may be that those properties' default values depend
on the type of object they are bound to. The most straightforward way
of dealing with this seems to be to defer determining the actual
default value until the respective FObj's bind() methods...
Does this sound OK, or does anyone see a better way?
It was my goal that all the properties should return the correct value
from the PropertyList.
That's what I suspected, hence my question.
If we consider inheritance in the following simple case:
<!-- no border precedence specified, so all default to 6 -->
<fo:table-column border-before-precedence="inherit" ... />
If I interpret the Rec correctly (5.1.4 Inheritance) the column
inherits the computed value of 6 from the table (as opposed to getting
its own default value of 4).
That complicates matters... but maybe only a bit, since I already
hinted at the other option: from within the property subsystem, check
the runtime-type of the FObj to which the PropertyList is attached, and
use that type to determine the default value.
My only remaining question is: where exactly should that happen?
Can anyone think of another property where the default value depends on
the type of object it is attached to? Maybe that'll give me some idea.
So if it is possible at all, I would prefer to see that the
inheritance issues is implemented in the PropertyMaker classes,
instead of the FObjs (or the LayoutManagers).
Oh, I definitely think it's possible. It will just take some more time
to figure it out.
Thanks for your input.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
-----END PGP SIGNATURE-----