Duplicate vs. “Save as” in Lion: How to set keyboard shortcut

Some of you might already have noticed that beginning with Lion, Apple’s started getting rid of the the “Save as…” functionality. Found on every major desktop operating system, it allowed for basic manual revision control. Apple revamped the whole save-system with Versions and the automatic save state feature.

You can use the new “Duplicate” feature to mimic the old functionality to some extend, although, you will have to adapt your workflow a little. When access duplicate from File ⇢ Duplicate, your current window is cloned, duplicated. You can then save it using ⌘S or from the menu bar like you used to and save it under a different file name.

By default, there’s no keyboard shortcut in place for “Duplicate”. You can access it from the menu bar or the small down-pointing arrow next to the window title of an already saved document. You can, however, choose to set a keyboard shortcut.

  • Go to System Preferences ⇢ Keyboard ⇢ Keyboard Shortcuts
  • Select Application Shortcuts
  • Click +

Duplicate-Shortcut

Set it to All Applications and enter “Duplicate” as Menu Title, it’s case sensitive, so make sure it’s written with a capital D.

Now enter your desired keyboard shortcut, but make sure you’re not using any existing global or application specific keyboard shortcut. This setting will have a higher priority, so don’t go for ⌘P or you will no longer be able to print with that shortcut.

You could go for the old “Save as…” shortcut ⇧⌘S. I think it it’s likely to be reused in the future or already in use in different Applications, so I recommend something like ⌃⌥⌘D.

Clear list of recent items in OS X Lion [ Dock / Exposé ]

In OS X 10.7 ‘Lion’, when you right-click an icon on the dock, it shows you a list of the “most recent” items for that application. The same files appear in the application exposé. For me at least, it also lists items I already deleted. Maybe it’s a bug, maybe it’s feature.

recent-items

I tried clearing the history through  ⇢ Recent Items ⇢ Clear Menu. That didn’t work. Turns out I was just looking at the wrong place. It’s a per application setting. You have to clear it for every single application. Takes a while, but once it’s done, it’s done.

And that’s how you do it:

  • Open the application.
  • Go to the menu bar
  • File ⇢ Open Recent ⇢ Clear Menu
  • Restart the application

If you don’t restart the application,it will keep the history until you do.

fullscreen mode and multi-monitor setups

Lion’s been out for a little more than a day now and it’s time for my first rant. There are a lot of things I like about it but there are also a couple of things that I don’t like. Like paper cuts, they won’t kill you, but once you notice them, they will drive you batshit insane mad.

safari screenshot

One of these paper cuts is the new fullscreen mode for applications. It makes great use of the limited screen real estate on single smaller screens, but the easy and quick access in mission control is where it excels. Single smaller screen? That’s right. It doesn’t mix well with multi-monitor setups. If you’re familiar with the concept of spaces you will know that in multi-monitor setups a space consists of the two (or more) screens. And that’s part of the problem. A fullscreen application, making use of the new Lion API, doesn’t take up a single screen, it takes up the whole space. It’s goes fullscreen on your primary screen, locking any additional screen on that same space. You get the blueish-grey linen background that’s also used in Mission Control and that’s it, you can’t place any windows on it, you can’t place anything on it. It’s useless.

It defeats the whole purpose of the fullscreen mode, decreasing effective screen real estate. One can only hope that Apple will fix it. However, I have to admit, I have my doubts. I can’t imagine this remained unnoticed throughout the developer previews. The only reasonable, and most disappointing, explanation seems to be that we’re dealing with a serious case of ‘working as intended’. Let’s hope I’m wrong about this one.

Lion’s most awesome new feature

I’ve read a lot of OS X 10.7 ‘Lion’ reviews and no one, not one mentioned that there’s a smiling pile of poo 💩. How are people not talking about this?

It’s part of the Unicode Emoji support that was brought ‘back to the Mac’ from iOS.

Unicode Emoji

Here‘s the fileformat.info page for the character.

You can use the HTML-code 💩 but it won’t display anything but a box unless your OS knows the character. So far it seems only to be working on Lion and iOS.

If you’re looking for a list of Unicode Emoji to use on iOS, take a look at www.mackeys.info on your iOS device. You can change the user agent to view it on Lion, but since it’s now part of the “Special Characters”-dialog, there’s little reason to. You can access the dialog by pressing ⌥⌘T in most apps.

Resizing images using the command line

If you happen to find yourself in the situation that you want to resize a large amount of images in OS X, you basically have two options:

  • Buy an App that does it for a couple of quid.
  • Use the tools that came with your OS.

If own a copy of Pixelmator you already have bought an App that’s capable of batch resizing images. Just take a look at Automator, Pixelmator added a few new actions to it.

But this is about using the tools Apple gave you, specifically sips.

scriptable image processing system

Continue reading

My take on the CoverSutra controversy

It’s been two days since the Mac App Store has been released and there has been a lot of confusion and a lot of anger. CoverSutra, an app to control iTunes and displaying CoverArt on the Desktop, in particular has caused controversy and is the first little scandal of Apple’s new software repository.

The application in question is developed by Sophie Teutschler, best known for her Apple Design award-winning iOS app Articles, an independent software developer from Germany. In spite of promising free updates until the next major release (3.0) of CoverSutra, she released version 2.5 exclusively on the Mac App Store. This caused a lot of angry comments, disappointed customers and supporters insulting each other, criticising or defending Teutschler’s decision.

I’ve been a CoverSutra user for a while, and I did buy the MAS-version of the app, the moment I saw it. I wanted to support the developer of a great piece of software. However, I did not know that there wouldn’t be any more updates for users that did not buy the new version. To be honest, I was quite surprised as the promise to provide existing customers with free updates is featured very prominently in the app itself, as well as being displayed upon registration. This isn’t only a promise, it’s an agreement the developer entered with her customers. They paid for the software, they fulfilled their part. She agreed to offer updates which she, according to her own words, simply forgot. Everyone makes mistakes, but it’s astonishing to me that she does not seem to acknowledge to making one but instead offered a list of pretty weak excuses. Contrary to the opinion expressed by a lot of supporters of disappointed users being cheapskates that just want to get everything for free, I really don’t believe it is about money. CoverSutra costs $5 on the App Store, and while it’s certainly worth every penny it does not change the fact that she did not honour her part of the deal. Imagine you had ordered a pizza and paid for it, only to find out that the delivery guy ate a piece, and then, when you called the place, they told you they had decided to give a piece to the delivery guy because he had forgotten to have lunch and got hungry. You’d be pissed. I certainly would.

I understand that independent developers don’t have the easiest job in the world, and having to deal with customers, especially an angry mob, isn’t easy either but one shouldn’t make promises one can’t keep. Fine, she forgot, but when then she was reminded, taking a step back and honouring her part of the bargain would have been the right thing to do in my opinion.

Here are Teutschler’s two blog posts, followed by a list of posts I read about the controversy.

——

And here’s what Pieter Omvlee, developer of apps like FontCase, Sketch and DrawIt wrote to me on twitter:

pieteromvlee
@mrigns It’s true that I don’t understand why she can’t keep pushing Sparkle updates. Takes no effort. But some people should get a life. :P
08.01.11 19:38
Posted in Mac