StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>There are a few options.</p> <ol> <li><p>Just use <code>Ctrl-Cmd-Shift-3</code> or <code>4</code> instead of <code>Cmd-Shift-3</code> or <code>4</code>. This does not save the file to the desktop, instead it saves the data in the clipboard/pasteboard. I don't know where's the official mention of this, but <a href="http://www.apple.com/pro/tips/secretcapture.html" rel="nofollow noreferrer">here is one</a>. Then you can get the data through <code>NSPasteboard</code>, see <a href="http://developer.apple.com/mac/library/documentation/Cocoa/Reference/ApplicationKit/Classes/NSPasteboard_Class/Reference/Reference.html" rel="nofollow noreferrer">here</a>.</p></li> <li><p>You can use <a href="http://developer.apple.com/mac/library/documentation/Darwin/Conceptual/FSEvents_ProgGuide/Introduction/Introduction.html#//apple_ref/doc/uid/TP40005289-CH1-DontLinkElementID_15" rel="nofollow noreferrer"><code>FSEvents</code></a> to be notified whenever a file is created in a specified folder. Then you can rename the screenshot file soon after it was saved to the desktop by the system. Note that the file name of the screenshot depends on the language environment you choose in System Preferences. So, be very careful if you want to make your program work on a non-English machine.</p></li> <li><p>If you just programmatically take the screenshot, you can use the command line tool <code>screencapture</code>, see the <a href="http://developer.apple.com/mac/library/documentation/Darwin/Reference/ManPages/man1/screencapture.1.html" rel="nofollow noreferrer">man page</a>.</p></li> <li><p>Of course you can hack into the system and take over the handling of <code>Cmd-Shift-3,4</code>, as <code>Snapz Pro</code> does, for example. You know what you're doing if you choose that way.</p></li> </ol>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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