Adobe Scripting Additions

I’ve been getting warning messages in my Console log stating the “Adobe Unit Types.osax” has deprecated functions. Then, when I starting scripting Xcode with AppleScript, I’ve been getting a bunch of errors about the above listed library. Well, Adobe had something to say about that: http://kb2.adobe.com/cps/516/cpsid_51615.html

Xcode Script Menu and P4

Here is another way that I am able to check out a file using the Xcode Script Menu and a keyboard hot key: #!/bin/sh # This shell script checks out the current file from Perforce # Get the file’s path components FULL_FILE_PATH=”%%%{PBXFilePath}%%%” SRC_FILE=${FULL_FILE_PATH##*/} FILE_PATH=${FULL_FILE_PATH%/*} # This line brings in my settings so that Perforce knows … Read more

Making sense of CrashReporter…

So, if I have a CrashReporter dump for a release application I am trying to troubleshoot, I found the following page very helpful: http://developer.apple.com/tools/xcode/symbolizingcrashdumps.html Essentially, I can take the crash report and find out what line of code the error occurred at. But, you have to have the source code in order to do this … Read more

Hey… where’d you go?

A co-worker of mine had trouble debugging his library in Xcode. For some strange reason, GDB would not stop at any of his breakpoints. He did the usual printf and NSLog to see if the code was even being called, and sure enough… it was. The only way he was able to fix it was … Read more

Exceptions are for programming errors

You should catch errors but be very careful about swallowing it and not re-throwing the exception. I have seen this in certain projects where exceptions are swallowed and the developer of the offending code never even knows that this happened. So months can go by without any testing, you are doing early testing … right?!… … Read more