Applications linked against iPhone OS 4 and later are automatically assumed to support multitasking and to implement the appropriate methods to handle transitions to the background state. However, work is still required to ensure that your application transitions smoothly between the foreground and background.

Therefore, if you set your Xcode project’s target to a Base SDK of 4.0, your application is expected to support multitasking. In some cases having your app moved to the background instead of being terminated may not be appropriate. It is possible to opt out of background execution by adding the UIApplicationExitsOnSuspend key to your project’s Info.plist and setting its’ value to YES. This effectively disables multitasking for your app and will force it to terminate instead of being suspended by the OS.

So I decided to write a small Automator application to automatically crop my screenshots. The application can be downloaded here. To use the application, drag the CropAction.action file to ~/Library/Automator and execute the iPhoneScreenshotCropper, selecting the image files you’d like to crop. The image files have to have one of the supported file extensions of png, jpg, jpeg, or tiff. They also need to have the correct resolution matching a full size screenshot from an iPad, iPhone, or iPod touch device. The existing image files selected will then have the status bar removed.

One caveat, I’ve only tested the application on PNGs so far.

svnmerge: command execution failed (exit code: 1)
svn merge -r 1:1 http://myrepo/svn/projectbranches/source.
Conflict discovered in 'dir/some-file.txt'.
Select: (p) postpone, (df) diff-full, (e) edit,
        (mc) mine-conflict, (tc) theirs-conflict,
        (s) show all options: svn: Can't read stdin: End of file found
svn: Error reading spooled REPORT request response

The source of the error is due to a conflict encountered due to the merge. However, due to a new feature in Subversion 1.5, svnmerge is unable to instruct Subversion how to proceed. The new feature is client based and called “Interactive Conflict Resolution”.

To resolve this issue and allow svnmerge to complete, I disabled the new feature. This is done by placing the following line in your Subversion config file:

interactive-conflicts = no

Of course this disables interactive conflict resolution for all further invocations of the Subversion client. So once svnmerge has completed successfully, be sure to set this option back to yes if you’d like to continue using this feature.

hibernate.format_sql

Setting this property to true will print out the generated SQL to the console. However, I’ve found having a separate log file that was solely responsible for capturing this generated SQL was invaluable. So how do we set it up with Logback?

<appender name="hibernate-sql" class="ch.qos.logback.core.FileAppender">
  <file>logs/hibernate-sql.log</file>

  <layout class="ch.qos.logback.classic.PatternLayout">
    <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>
  </layout>
</appender>

<logger name="org.hibernate.SQL">
  <appender-ref ref="hibernate-sql"/>
</logger

This will put all our generated SQL statements from Hibernate into the hibernate-sql.log file.

unrecognized selector sent to instance

There is an Apple tech note that explains how to resolve this – QA1490

To resolve this issue, the static library should pass the -ObjC option to the linker. This flag causes the linker to load every object file in the library that defines an Objective-C class or category. While this option will typically result in a larger executable (due to additional object code loaded into the application), it will allow the successful creation of effective Objective-C static libraries that contain categories on existing classes.