Last week, I set up a calendar appointment on my Mac. I use ( Macworld rated 4.5 out of 5 mice ), but the same thing would have happened in iCal. I entered the appointment as a reminder for my wife (we share the same calendar). I set the alarm to go off later in the day, at a time when my wife wanted to be reminded of the task. The alarm went off exactly as scheduled on my Macs and linked iOS devices. It did not go off on my wife’s iPhone (the critical device in this scenario) or her iMac.

I was surprised because I was fairly certain that I had done this alarm setting on prior occasions, and the alarm had gone off on my wife’s iPhone. I checked on the web. Others confirmed my memory; a set alarm would go off on all devices sharing a calendar. In fact, most comments were to complain about this behavior. Unlike my situation, people wanted to be able to set an alarm for themselves without having it bother those who shared their calendar. They couldn’t. Now the situation appeared to be the reverse!

I contacted the good people at , to see if they could shed more light on this matter. They could. They informed me that Apple had apparently silently made a change to iCloud a few weeks earlier, probably in response to all the user complaints. Alarms now only get enabled on devices owned by the user who created the event. The event itself appears on all shared calendars, but not the alarm. As far as I can figure out, this is not a configurable option. You were stuck with this being one way before and stuck the other way now.

I have had a long-standing problem where there is often a slight delay when I begin to type after a pause. The result is that the first two letters get reversed. For example, if I type “The,” it appears as “hTe.” This will happen almost every time, continuing for days, and then inexplicably stop — only to return again a few days or weeks later. Several forum postings suggested that ( Macworld rated 4 out of 5 mice ) might be the root cause. I asked the people at about this, and they acknowledged that TextExpander was a “possible cause” in some “edge” cases. The good news is that they believe they’ve squashed this bug in the just released version 4. I’ve been testing a beta version of the upgrade over the past weeks (and I’m now running the release version) and can confirm that the symptom has vanished (hopefully never to return).

Installing an update is a bit like having surgery. The intention is always to make things better and most times you are pleased with the result. But there’s a small risk that something will go wrong, leaving you worse off than you were before. Such is the case with two recent Apple updates.