-
Another Lion change wreaking havoc
One common practice when subclassing a class is to use an application specific prefix so that if Apple adds a similar class in the future, it doesn't conflict. For ReceiptWallet, I always used RW. One of the classes I subclassed was NSTextView so that I could draw text in gray when no text is entered. This is similar to NSTextFieldCell's setPlaceHolderString method. I named my member variable placeHolderString and added a property. The code worked fine on Snow Leopard, but when it was run on Lion, we had reports that the placeholder text was drawn twice and blurry.
-
Bit by API Changes
Mac OS X Lion has changed some of the internal workings of various APIs and as I don't work much on Mac apps, I didn't care too much. However, one app I work on got bit by this pretty hard. In various places in the NSDocument based app, I called:
-
Goodbye old friend (Quicken)
Back in April when there was a lot of talk about Mac OS X Lion coming out and it not supporting Rosetta. As I relied on Quicken for my accounting and have been using it for almost 20 years, I decided to start looking for a replacement sooner rather than being forced to make a decision when Lion came out. Intuit was pretty quiet about what was happening with Quicken and considering the last real Quicken version was Quicken 2007 (Quicken Essentials could only give me a snapshot of my investments and not track them), I didn't have high hopes for an Intel native version of Quicken coming out for Lion.
-
The Art of Googling
Several years ago, I wrote about how librarians will become experts in web searching. While I still believe that this is true, there is no reason that everyone can't become masters at getting good search results. Lately, I've noticed that the ability of people to effectively search using a search engine (my engine of choice is Google) is quite limited and if people learned how to search better, it would really help them.