On 2010-02-17, at 17:53, Max Carlson wrote: > The original intent was to warn when someone forgot to include a default > stylesheet or included the wrong one.
So rather than a global flag, wouldn't it make more sense to have a per-attribute flag that turns this warning off? If you turn the warning off globally by default because the warning creates too much noise for your code, then anyone who turns the warning on to debug something else will be swamped by the same noise. > In my case, I have a bunch of color attributes that can be optionally > defined with CSS, but don't have default values or have a constraint in > the value field. At init time, if the optional values aren't set, I set > them based on a base color. So I don't want/need the warnings in this > case... Is it not sufficient to simply provide a value of undefined (void 0) for your colors. That should turn off the warning, but still let you detect that no color was assigned. That's the intent of the current code. If that doesn't work for you, then re-open the bug to me and I'll make that work. _______________________________________________ Laszlo-reviews mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-reviews
