Best new Outlook 2007 feature: Do Not Save sent message

I don’t have a lot of warm feelings about the Office 2007 “Quick Access Toolbar” or most any new Outlook 2007 feature, but there is one killer feature that the two of ‘em together give you.

You can configure the Quick Access Toolbar so that you click a simple checkbox and any message you send is not saved!

Okay, so why should you care?

Well, for those of us who live by full text search Outlook “Sent Items” are a goldmine. I don’t bother sorting mine – every few months I dump a few thousand into my PST “Save” folder and make space on Exchange. I routinely use Windows Search 4 to find answers to important questions in seconds. It’s been my biggest cognitive computing boost since Google replaced Alta Vista.

Problem is, the Sent Messages also contain thank you notes, social messages, acknowledgements, and other noise. It’s tedious to delete those, so I typically leave them alone and only delete them when they show up in searches.

How much better then, never to save them at all. If only there were a one click method to not save those “thank you” notes…

Now there is …

 

Now when I send a simple email that I don’t want to clutter future search results, I just click ‘Do Not Save’. No more junk in my Sent Items list! (I don’t use email for anything very sensitive, so that use case doesn’t apply.)

In order to set this up you need to:

1. Start a new email message. This is the only way to see the email-specific “quick access toolbar”. (In Outlook 2007 the ribbon bars and quick access toolbars are distributed throughout the various Outlook data types such as Appointment, Tasks and so on. Yes, Outlook 2007 really is a train wreck.)
2. Click the Quick Access Toolbar customization drop down to the right of the toolbar and select “More Commands”
3. Customize as you wish (There are lots of interesting options, but many do not have distinctive icons. See “train wreck”, above.) Here’s where to find the “Do Not Save” control:
   

Update: Note that the Quick Access Toolbar you see when viewing a message is different from the Quick Access Toolbar you get when editing a message. Remember – Outlook = “train wreck”.

Killing an undead XP Active Desktop

Active Desktop rose from the grave the other day. It’s probably something that our corporate IT group unwittingly unleashed.

The symptom was that when I tried to drag an Outlook attachment to the desktop XP mumbled something about creating an Active Desktop bitmap.

Yech.

Active Desktop is only supposed to run when you’ve checked some boxes in the Display Properties:Desktop:Customer Desktop menu, but I had a bad case anyway. It was undead.

Of course there’s an obscure registry option to kill it forever. There usually is in the Windows world. I found 3 good articles with different sets of advice:

• Think and Create- How to Remove Active Desktop in Windows XP
• Disable Active Desktop feature in Windows. « geek-o-pedia
• How to disable Active Desktop in Windows XP - MyTechSupport.ca

Surprisingly, even knowing the registry key(s), I couldn’t find any article on support.microsoft.com. That’s usually a great resource. Here are the keys …

• HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoActiveDesktop
• HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\ForceActiveDesktopOn

Check out the above articles for the details. Everyone recommends the first key, one reference suggested the second key as well. I did both and, after a restart, my undead Active Desktop is back in the grave.

I assume Microsoft finally staked this vampire in Windows 7? Active Desktop was one of their dumber ideas.

Hold off on buying those Nehalem i7 Macs?

Via Slashdot, a Microsoft support document tells us the new Nehalem CPUs have some significant bugs...

Stop error message on an Intel Xeon 5500 series processor-based computer that is running Windows Server 2008 R2 and that has the Hyper-V role installed: "0x00000101 - CLOCK_WATCHDOG_TIMEOUT"

...This problem occurs because spurious interrupts are generated on the computer that uses Intel code-named Nehalem processors. These interrupts are caused by a known erratum that is described in the following Intel documents....

I'm close to buying one of the Nehalem iMacs, but it's not urgent. So I can just hold off for a few weeks and watch how this plays out. All CPUs have bugs, and new CPUs can have grave bugs. If this is a bad one we'll find out soon enough.
--
My Google Reader Shared items (feed)

Amazon has an Apple Store?

I didn't realilze Amazon had an Apple Store. I've always found Apple stuff there by searching on it, this is much better. Unfortunately today they are listing very few iMacs, I wonder if the supply has run out.

Incidentally, the above link is from Gruber's Daring Fireball, so if you use it and buy I think he should get the credit.
--
My Google Reader Shared items (feed)

Using OS X 10.5 iCal with Google CalDAV - cleaning up import disasters

I don't have a rich enough vocabulary to fully express my opinion of OS X iCal. Can a worse calendar program exist anywhere or anywhen?

And yet ... Google lists iCal as one of precisely two products that will work with Google's CalDAV services. I now use CalDAV with my iPhone, and at the moment I prefer it to iPhone ActiveSync.

That's nice, but not enough to make me bother -- until a recent Google Calendar import misadventure. Google doesn't give users a way to remove all events from a Calendar without deleting the calendar. I need something more powerful than Google's anemic calendar interfaces.

I decided to give iCal CalDAV a try with Spanning Sync as my backup.

First I had to clean out the old calendars, now abandoned since I'd moved my calendaring to Google. It was easy to delete all but the Home Calendar. You can't remove the iCal Home calendar [SEE UPDATE: This was a bug, you should be able to remove it.], and there's no UI to delete all Home Calendar entries (the iCal List view, in particular, having been famously deleted in 10.5 and replaced with the bizarre "." workaround).

I tried the "search on ." method to find entries in a list view and delete them, but there were several undead entries. They returned after deletion. Besides, iCal is sickeningly slow at delete operations.

In the end I had to remove all data in iCal using the Finder:

... Navigate to the folder ~User/Library/Calendars
Delete the contents

Navigate to ~User/Library/Application Support/iCal
Delete the contents...

Once that was done I followed Google's CalDAV setup directions. I now have about five of my Google Calendars in iCal. It's a good way to view a lot of Calendar data in one place.

In early testing, things look promising. I can in fact edit and delete CalDAV entries and the changes are reflected back to Google -- at one time I believe that didn't work. Alarms, however, don't get set in Google even when they're set in iCal.

Update: The directions work for Google Apps domains as well as standard Google Accounts. See also.

Update 11/29/09: You should be able to delete your Home calendar. I found this out while setting up iCal on some of our other machines. When I right clicked on Home the Delete function was black, it had been gray on the first machine I worked with. I went back to the initial machine, my old G5 iMac, and I was able to delete it there as well. I think this was related to the "zombie" recurring appointments (dated 2002) that I couldn't remove. When I deleted all the Calendar data in the Finder I cleared up that problem -- and the problem of the unremovable "Home" calendar. The most likely cause? Permissions, of course. The OS X permissions model needs to be shot.

--
My Google Reader Shared items (feed)

When you can't use a signature with iPhone mail ...

The iPhone Mail.app was originally designed to work with a single account. So it had a set of preferences that made sense for a single account.

When Apple added support for multiple accounts, they did a pretty good job redoing Mail.app. Except, of course, for the preferences.

Even though I now get my business email and personal email on my iPhone, I have only one signature. Since the only thing that's common between my business and personal email is my name, there's not much use for that signature. I've removed it.

Since you don't see the signature when you compose a message, this is a bit of a subtle problem. It could even be embarrassing if, for example, your personal signature was a bit risque.

--
My Google Reader Shared items (feed)

Why is the App Store boring and buggy?

I visit the iPhone App Store fairly often. Excluding games, most of the Apps that I look at are either dull or buggy -- and even good 3rd party apps are slow compared to Apple's apps. Even some of the apps I used to use, like Byline.app, have become unacceptably buggy. Others are clones of applications I'm currently satisfied with.

Why is this?

I'd like to know. I'll hazard some guesses.

My first guess is that the current iPhone APIs are buggy. Apple's own iPhone apps are pretty responsive and reliable, but, obviously, Apple developers have insider knowledge. Perhaps Apple can use less buggy private APIs, or knows what to avoid.

My second guess is that it's very hard to write an innovative iPhone App. You can't use Location, because there's no background API for that [Corrected thanks to a comment]. You can't mess with the Calendar, because there's no API for that. You can't do anything resembling an Apple product because your App will be rejected. Maybe the dev environment is so challenging that, in addition to the above, you have to be a real hot developer.

A contributing factor is that the non-game developer market is oddly small. For competitive reasons Adobe and Microsoft don't do iPhone development. Apple itself doesn't sell iPhone apps. Google would like to play, but Apple's effectively banned them.

If you add up all of the above, there are very few people have both the capability and the motivation to do non-game iPhone development.

So the (non-game) App store is boring and buggy.

Any other explanation?
--
My Google Reader Shared items (feed)