Databases
StackOverflow2013
Postsdbo
POBest Way to Handle Errors with AppleScript-ObjC embedded in Cocoa App?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBest Way to Handle Errors with AppleScript-ObjC embedded in Cocoa App?
    primarykey
    data
    text
    <p>I'm invoking a small AppleScript handler from within a larger Cocoa/Objective-C app (using the AppleScript-ObjC framework to call the AppleScript methods directly from the Objective-C code). I originally tried using Scripting Bridge, but that didn't work for me due to compatibility problems with the external app. The only purpose of the AppleScript is essentially to send a small string to the external app. This is the first time I've attempted to do something like this in order to control an external application, so please bear with me if I'm making an obvious mistake.</p> <p>Occasionally, the AppleScript may encounter errors depending on the state of the external application, and I would like to handle those errors appropriately in my Objective-C code.</p> <p>The way I'm doing this right now is that I have a try block in the AppleScript:</p> <pre><code>try -- Do stuff return the number 0 on error the error_message number the error_number return the error_number end try </code></pre> <p>I return zero if the script finishes normally, and return the error number if it doesn't. Then in the Objective-C code, I test the return value and throw a "normal" exception in cases where there is an error, so that I can handle that in my regular exception-handling code.</p> <p>This works, but is there a way to trap the AppleScript exception directly from the Objective-C code? When I run the code without the AppleScript <code>try-error</code> code in XCode, it seems that it hits my exception breakpoint before it returns from the AppleScript, but it never invokes the <code>@catch</code> block for <code>NSException</code>. Is there some way to catch that exception that is being hit somehow? I'm guessing the answer is no, but I wanted to check that there isn't some better way to do this than what I'm doing. Apple's documentation on AppleScript-ObjC is rather sparse, and mostly just discusses handling errors within AppleScript.</p> <p>Update: So, I just tried playing around with the breakpoint setup a little bit, and it turns out that it's a C++ exception being sent from the AppleScript code, not an Objective-C one. That's why it wasn't being caught by the <code>@catch</code> block I was using. It seems that the AppleScript-ObjC mechanism uses exceptions for control flow/recoverable errors, and I had my breakpoint set up to break when they are thrown. So, I think it's probably best to just catch the errors in the AppleScript application, and return an error code as a string or integer to the Objective-C code.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmnemia
    1. USmnemia
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBest Way to Handle Errors with AppleScript-ObjC embedded in Cocoa App?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POBest Way to Handle Errors with AppleScript-ObjC embedded in Cocoa App?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POBest Way to Handle Errors with AppleScript-ObjC embedded in Cocoa App?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI can't answer your question specifically, but I'll point out that in Objective-C/Cocoa, exceptions are meant to indicate truly exceptional conditions, typically due to programmer error rather than errors that can be safely recovered from. From the [documentation](http://developer.apple.com/library/ios/#documentation/cocoa/conceptual/Exceptions/Articles/ExceptionsAndCocoaFrameworks.html): "The Cocoa frameworks are generally not exception-safe. The general pattern is that exceptions are reserved for programmer error only, and the program catching such an exception should quit soon afterwards."
      singulars
      1. POBest Way to Handle Errors with AppleScript-ObjC embedded in Cocoa App?
      1. USAndrew Madsen
    2. COThat's a good point, although some of the errors that could be coming from the AppleScript could well be unrecoverable errors. The only reason I ask that is that invoking the AppleScript code DOES seem to raise an exception that hits my exception breakpoint even for minor, recoverable errors...but it's not a normal Cocoa NSException, from what I can tell. So I just want to know if I can catch that from my Objective-C code (as opposed to AppleScript) somehow.
      singulars
      1. POBest Way to Handle Errors with AppleScript-ObjC embedded in Cocoa App?
      1. USmnemia
    3. COInteresting. How have you setup your exception breakpoint? What does the stack trace look like when the breakpoint is tripped?
      singulars
      1. POBest Way to Handle Errors with AppleScript-ObjC embedded in Cocoa App?
      1. USAndrew Madsen
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload