Thanks!
On 11.08.2006, at 16:19, Mike Schrag wrote:
> So are you saying it has an error on the left of the '=' or the
> right of the '=' on the binding assignment? I'm assuming that
> you're getting an error at all means you have the "Check Binding
> Values" enabled under WOLips=>WODEditor preferences? One thing
> you can do is add a "// VALID" to the end of the binding line,
> which hints to binding validator that the line in question is
> actually NOT an error ... If this happens a lot, though, that can
> be pretty annoying. The check for implementing KVC is not a bad
> idea, except that WOComponent implements KVC, so if we did that
> check, you'd lose all WOComponent binding keys, which effectively
> means you lose ALL binding checks, because once you lose any
> binding in a key path, you can't check anything to the right of it.
>
> You can also just turn off binding value checks :)
>
> ms
>
> On Aug 11, 2006, at 6:02 AM, tecc wrote:
>
>> Hi,
>>
>> thanks for the response to the last question. Here comes another
>> issue, although
>> thats more of a suggestion: when editing components and putting in
>> paths to
>> classes that implement key value coding, like D2WContext, the
>> component editor
>> tells me I have an error.
>>
>> For instance: Assume binding a formatter in a WOString to
>> d2wContext.formatter,
>> then the d2wContext.formatter keypath does not exist. However it
>> is resolved during
>> runtime. We have a couple of things like that, and the component
>> editor marks those
>> up as errors.
>>
>> How about checking if the class one is binding to implements KVC,
>> and in case it
>> does degrade the error to a warning? Or how about making them
>> warnings anyway?
>>
>> Just an idea,
>>
>> J.L.Simon
>
This archive was generated by hypermail 2.0.0 : Mon Aug 14 2006 - 05:29:42 EDT