Saw this, figured that on the off-chance this saves me some aggravation that that aggravation would be worth $3.99. Saw the words "my store" and realized that in all likelihood I'd have to type out my entire credit card number, billing address, email address, potentially create a password, and came to the conclusion that <i>that</i> level of immediate aggravation would offset the potential of saving me future aggravation. Went to the App Store hoping that I could pay you there with a sum effort of maybe 25 key presses, total. Found that I couldn't and was disappointed. Please get this on the App Store, let me give you my money.
Just today I was wishing that Chrome's Hold-to-Quit functionality was an OS-wide feature. Thank you very much for creating this, it was an instant purchase in my book.
"Ever hit ⌘Q and accidentally quit an application when you really meant to press ⌘W and close a window?"<p>At first I was really puzzled when I read this sentence...Q and W are so far apart on the Dvorak keyboard! ;-)
System Preferences -> Keyboard -> Keyboard Shortcuts -> App Shortcuts -> + -> select app, menu entry is usually "Quit <appname>", and set it to cmd-ctrl-q, or something similar.<p>(There's probably a more generic way by editing your <i>~/Library/KeyBindings/DefaultKeyBinding.dict</i>, but I'm not sure what the appropriate selector would be)<p>Of course, these just change the binding, the 'hold to confirm' is quite a nice UI feature.<p>Edit: The reference I was remembering is <a href="http://www.hoboes.com/Mimsy/hacks/disabling-quit-rewriting/" rel="nofollow">http://www.hoboes.com/Mimsy/hacks/disabling-quit-rewriting/</a> and appears to still work in Lion. Still on a per-app basis though.
If you're looking for other nice and useful little Mac keyboard command utilities, I implemented shake to undo: <a href="http://www.natestedman.com/post/shake-to-undo-for-mac-os-x/" rel="nofollow">http://www.natestedman.com/post/shake-to-undo-for-mac-os-x/</a>
This makes no sense to me. It says it stops cmd-Q from losing your work. Every program I have seen asks if you want to save unchanged edits before it closes the window following reception of a quit. Now, Lion has a new paradigm available for quitting, but it autosaves and versions all unsaved edits, so you also don't lose your work. How are people losing their work from pressing cmd-Q? In 25 years of using Macs off and on I've never had that problem.
Very cool idea. I don't know if I'll personally use it; as a dvorak user, it's harder to accidentally hit cmd-q when you mean it hit cmd-w. Then again, it's also easier to hit cmd-q some times because the q sits just above the cmd.
I would have loved to have had this a year ago, or two, etc., but my accidental quits haven't been nearly as frustrating since upgrading to Lion. I can still see this being useful, though, especially with apps that are slow to implement resume functionality.
I've been wanting/needing something like this forever. One thing I noticed is that the '30 days' menu item isn't removed until the app is restarted. Maybe you could automatically restart the app after registration?
It would be great if there was a way to bypass or disable CommandQ temporarily.<p>Like an option in the menu, or something else (not sure what) for people like me who have the menu bar icon disabled.
The idea is definitely good, but I think the "problem" it solves might be overrated - after all, if an app has unsaved content, it will ask you to verify your action, so you never really lose anything but a second or two of time restarting the application the few times you do this mistake, if at all.