Debugging bindings with -NSBindingDebugLogLevel 1

  • I tried adding '-NSBindingDebugLogLevel 1' (no quotes) to "Arguments Passed on Launch" to my scheme, and I also wrote it to the app's defaults. But I don't see any logging when I've got an error (in this case, a deliberately mis-spelled key path).

    Am I doing something wrong, or is this not one of the things it logs?

    TIA,
    Rick
  • I finally did see a rather unhelpful debug message from bindings. Not sure which setting actually triggered it, but I guess it's working.

    On Jul 7, 2012, at 21:41 , Rick Mann wrote:

    > I tried adding '-NSBindingDebugLogLevel 1' (no quotes) to "Arguments Passed on Launch" to my scheme, and I also wrote it to the app's defaults. But I don't see any logging when I've got an error (in this case, a deliberately mis-spelled key path).
    >
    > Am I doing something wrong, or is this not one of the things it logs?
    >
    > TIA,
    > Rick
  • On Jul 7, 2012, at 10:41 PM, Rick Mann wrote:

    > I tried adding '-NSBindingDebugLogLevel 1' (no quotes) to "Arguments Passed on Launch" to my scheme, and I also wrote it to the app's defaults. But I don't see any logging when I've got an error (in this case, a deliberately mis-spelled key path).
    >
    > Am I doing something wrong, or is this not one of the things it logs?

    It is helpful to keep in mind that bindings are actually made up of three different technologies, if you will, each with their own exception handling. Invalid key paths, for instance, fall under the purview of Key-Value Coding, which would throw an undefined key exception.

    HTH,

    Keary Suska
    Esoteritech, Inc.
    "Demystifying technology for your home or business"
previous month july 2012 next month
MTWTFSS
            1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30 31          
Go to today