Re: components with incorrect error labels

From: Hugi Thordarson (hug..efsyn.is)
Date: Fri Mar 09 2007 - 09:34:24 EST

  • Next message: Francis Labrie: "Problem running a WebObects application"

    Wow, en error-free workspace looks really beautiful :-).

    Thanks Mike, I owe you a beer (and I guess now I'll actually have to
    stand by it at the WWDC. Can't hide behind my usual excuse of being
    stranded in the middle of the North Atlantic)

    Cheers,
    - Hugi

    On Mar 9, 2007, at 2:19 PM, Mike Schrag wrote:

    > Your problem is a syntactic failure. // VALID is only a message to
    > the keypath validator for non-syntactic failures (i.e. missing
    > keypath). You can try adding "/" to the list of approved
    > characters in the WOLips Preferences for WOD editor.
    >
    > ms
    >
    > On Mar 9, 2007, at 8:50 AM, Hugi Thordarson wrote:
    >
    >> Hmmm, that's very useful. But doesn't seem to work for me. I wrote
    >> a resource handler to construct URLs (to external resources on my
    >> webserver) from keypaths. Anyway, long story short, I have a lot
    >> of bindings that look like this:
    >>
    >> src = application.swresourcehandler.img/new/transfer_arrow.gif;
    >>
    >> WOLips is not happy about the slashes in these keypaths, so most
    >> of my components don't validate. Adding // VALID at the end of the
    >> line does not seem to help. Any ideas?
    >>
    >> Cheers,
    >> - Hugi
    >>
    >>
    >> On Mar 9, 2007, at 11:43 AM, Mike Schrag wrote:
    >>
    >>> If you add a "// VALID" at the end of the line, it will tell the
    >>> validator to ignore the problem.
    >>>
    >>> ms
    >>>
    >>> On Mar 9, 2007, at 2:44 AM, Jean Pierre Malrieu wrote:
    >>>
    >>>> I have another (related) problem now:
    >>>> My wod are marked with red error underlining and icons for key
    >>>> paths.
    >>>>
    >>>> ex:
    >>>>
    >>>> PopUpButton2: WOPopUpButton {
    >>>> displayString = levelItem.levelName;
    >>>> item = levelItem;
    >>>> list = levelList;
    >>>> noSelectionString = "Tous";
    >>>> selection = subjectDisplayGroup.queryMatch.level;
    >>>> }
    >>>>
    >>>> The selection binding is marked with the error: "there is no key
    >>>> path 'subjectDisplayGroup.queryMatch.level' for page X.
    >>>> Obviously there is no such binding because queryMatch is an
    >>>> NSDictionary.
    >>>> Should WODEditor be validating such key paths?
    >>>>
    >>>> JPM
    >>>>
    >>>>
    >>>> Le 8 mars 07 à 17:01, Zak Burke a écrit :
    >>>>
    >>>>> Mike Schrag wrote on 3/8/07 9:47 AM:
    >>>>>> What does Problems View show?
    >>>>>
    >>>>> Aha. My bad. I do have an error: there's a binding in the .html
    >>>>> file
    >>>>> that isn't in the .wod file.
    >>>>>
    >>>>> I missed this for two reasons:
    >>>>>
    >>>>> 1. I had a poorly defined filter on the error messages that was
    >>>>> masking things from the Problems View.
    >>>>>
    >>>>> 2. Neither the .html nor the .wod pane show the red x error bubble
    >>>>> icon. I kinda expected the .html pane should show an error
    >>>>> since
    >>>>> it points to an undefined binding, just like a call to
    >>>>> SomeClass.undefinedMethod() would.
    >>>>>
    >>>>> But really, the problem was my stupid filter in (1). Sorry to
    >>>>> bother
    >>>>> you with problems that aren't your problems.
    >>>>>
    >>>>> zak.
    >>>>>
    >>>>>
    >>>>>> On Mar 8, 2007, at 9:39 AM, Zak Burke wrote:
    >>>>>>> Occasionally, I find the Package Explorer will label one of
    >>>>>>> my WOComponent files as containing errors when there are
    >>>>>>> none. Here's a screen shot:
    >>>>>>>
    >>>>>>> http://cobweb.dartmouth.edu/~zburke/error.png
    >>>>>>>
    >>>>>>> The errors can show up even in components where no changes
    >>>>>>> have been made. Running validation doesn't help, nor does
    >>>>>>> cleaning and rebuilding. Are validation errors cached
    >>>>>>> somewhere? Is there a way to kick the cache?
    >>>>>>>
    >>>>>>> zak.
    >>>>>
    >>>>>
    >>>>>
    >>>>
    >>>
    >>>
    >>
    >



    This archive was generated by hypermail 2.0.0 : Fri Mar 09 2007 - 09:34:33 EST