On Sat, 24 Sep 2005 05:22 pm, Andreas L Delmelle wrote: > On Sep 24, 2005, at 10:39, Andreas L Delmelle wrote: > > On Sep 24, 2005, at 03:36, Manuel Mall wrote: > >> <snip /> > > > > Thanks for the info Manuel. > > Ok then: > Instead of using hasPadding(), which tries to evaluate the specified > value, we could also provide a method hasPaddingInfo() (analogous to > the hasBorderInfo() method I added yesterday). > > This method would just check if the padding is null for every side, > without doing any evaluation. It would allow the check to remain in > the FOTree --the user would get a warning *if* padding was specified, > no matter whether it ultimately evaluates to zero or not, just as a > hint that the eventual value will be ignored by layout. > Yes, that's certainly an option and will probably catch 90% or more of real life cases. > > > Cheers, > > Andreas
Rgds Manuel