Thank you Tcuker. That is exactly the issue.
P T Withington wrote:
I would have believed that a while ago, but have been informed that
our model of libraries is apparently that they are textually included
(unless they already have been) and that top-level elements in the
library apply to the including element (typically the canvas). So,
'library attributes' are really 'canvas attributes'.
So, it is an error for more than one library to declare the validate
attribute (binary or not).
[cc-ing Sarah]
But I believe Sarah's complaint is that she has one library with
validate declared, which is included many times, and that she does not
get a warning, unless the library is binary-compiled.
On 2007-08-16, at 16:36 EDT, Philip Romanik wrote:
Hi Tucker,
If you have two binary libraries, each one that sets the 'validate'
attribute, you will get a warning when the libraries are included by
the canvas. It seems to me that the validate attribute should be
local to a binary library and not apply to the canvas. Do you agree?
If you don't agree, here is a scenario to consider. A binary library
has the line,
<attribute name="validate" value="false"/>
in it. When this library is included by the canvas, validation is
turned off for the canvas as well.
Thanks!
Phil
