12/12/2023 0 Comments Totalfinder apple eventsWhen this happens, I also cannot get the “ Reveal in Finder” feature in OS X’s own Spotlight interface to work. But occasionally, when I press Return after typing a query in LaunchBar, nothing happens. For example, I frequently use LaunchBar’s built-in interface for entering a Spotlight search query, which is better than OS X’s built-in interface because it only starts the search when you press Return. I believe I have also seen a similar problem in Photoshop CS6 on occasion.Īnother problem that is new in OS X 10.8 for me is the fact that sometimes, there are apparent glitches in the communication between applications. Clicking on them fails to bring them to the foreground, and they are not listed in the “ Window” menu as currently open document windows in Word:Īs you can see in the screen shot above, Word 2011 says that I have no document windows open, and yet there is mostly definitely a Word document window open in the background. Quite often, after a reboot, I end up with Word 2011 in a rather weird state, where there is both a foreground document window that I can work with and one or several background document windows that somehow remain inaccessible. Microsoft Word is another application that seems to be affected by similar issues. But I certainly didn’t have any such problems in Lion. I haven’t had time to investigate this further. I don’t know if this is somehow due to the fact that I still have several aliases to BBEdit documents and projects in my BBEdit Startup Items folder, since this probably conflicts with OS X’s built-in architecture for reopening documents. I end up having to force-quit BBEdit and relaunch it, and after that things work fine. For example, more often than not, after a reboot, OS X appears to reopen BBEdit for me with all its document windows, but when I switch to BBEdit, I get the Spinning Beach Ball of Death and the foreground document window is greyed out with a spinning wheel animation in it that goes on forever. But it certainly happens quite often for me.)Īnother problem that I have noticed is that, after a reboot or restart, OS X 10.8.2 often fails to restore certain third-party applications in a usable state. (Since I don’t trigger kernel panics for fun, I haven’t been able to verify that this occurs 100% of the time. OS X’s Preview seems to have the same problem. I have to reopen them manually via the “ Open Recent” menu. But when I have a kernel panic, after the reboot TextEdit reopens with zero document windows. If I quit and relaunch TextEdit, it correctly reopens all the appropriate document windows. It’s only a problem after a kernel panic. I’ve also noticed that, whenever I have a kernel panic, after I restart my computer, several OS X applications, including TextEdit, fail to reopen the document windows that were open at the time of the crash. I’ve already talked about the selection highlighting issues after hiding background applications. Update (): It looks like this bug may be back in Mac OS X 10.9 Mavericks.Apart from the kernel panics, OS X 10.8.2 is a fine release (it fixes the most outrageous flaw in Mountain Lion, which was the crazy behaviour of the Save As architecture). Update (): The bug appears to be fixed in Mac OS X 10.8.3. Update (): This bug also seems to cause hangs at launch for applications using the Growl 1.3 SDK. Of course, we hope that Apple will eventually fix the bug. Medium-term, the applications sending the events can be rewritten to use typeKernelProcessID rather than typeSignature or typeApplicationBundleID to specify the target application. The bug can also affect TotalFinder and applications that use the ODBEditor events.Īs a short-term fix, you can log out of your Mac or kill the appleeventsd process. This affected his iPhoto Library Manager as well as e-mail clients such as MailMate, Postbox, and GyazMail communicating with SpamSieve. The basic outline of the problem is that sometimes a particular application will get into a state where any events sent to it using AESendMessage (or AESend, for that matter) would not be delivered to the target application, and AESendMessage would simply block until the timeout value was reached, then return an errAETimeout error code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |