DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=38282>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38282 ------- Additional Comments From [EMAIL PROTECTED] 2006-01-31 22:37 ------- OK, just looked it up, and it seems like it *is* possible --although I wouldn't dream of it myself to do so, that's another issue. Then again: this problem will always pose itself, and it is not so much a matter of 'early property evaluation'. All properties are evaluated early, and some need to come first because of possible dependencies of other specified properties (i.e. relative font-sizes or core function calls). In itself, this isn't wrong, but the solution may be to postpone the whole property evaluation cycle for a marker and *all* of its descendants until the marker is retrieved (since we cannot possibly know how inherited properties specified on the retrieve-marker or its containing block will affect the properties of the markers and its descendants... Maybe this is another case where we absolutely need to keep a reference to the original PropertyLists instead of binding the individual properties to instance variables (?) I'll apply the patch as is, with a few added comments indicating that markers still need to be treated with caution. Cheers, Andreas -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
