14 Jan
2008
14 Jan
'08
2 p.m.
I've just upgraded Skim to 1.0.3, and now I find that Skim does not activate when the document is updated, bringing its behaviour into line with that of the other previewers.
Do other people see the same, and, if so, does this affect whether or not we want to activate the document after refresh? We could do something like
tell application "Skim" to tell (documents whose path is "/path/to/file.pdf") revert activate end tell
to avoid a second invocation of osascript.
Robin