This is an update regarding my original post on May 5 called Tiger Breakage. </p> <p> It turns out that two out of those three problems which were reported by my testers are not problems at all. The third has already been fixed by me. :) </p> ...
The weather's getting better where I live, so I'm spending more time on things that are necessary this time of year. Cutting the lawn, cleaning my barbecue, washing the car, and other things that need to be done. This stuff has been completely neglected...
Check out the first screenshot at the NetNewsWire 2.0 page. </p> <p> Thanks for catching that one, Gus! </p>
I recently finished coding a new feature that I will include in the 1.2.1 release (which should be coming out shortly). For a while, I started to notice that FuzzMeasure documents were getting larger and larger, but I didn't have any reason to slim...
Tiger manages to do a great deal of Jean Claude Van Damage to FuzzMeasure. Here are a few things that were noticed: </p> <p> <ul> <li>Slightly more noise in the frequency response display than with Panther. I'm not sure yet if this is related to drawing...
For all you faithful blog-followers, I will reward you with the most advanced notification of FuzzMeasure's release. Please, take a look at the new site before I go and alert the press tomorrow. </p> <p> It's exciting to finally get a product out...
I'm slowly working through the last few things that are required to get FuzzMeasure out the door. During these last steps, I finally disabled the eSellerate SKUs attached to FuzzMeasure, which means that nobody can purchase FuzzMeasure 1.1 anymore...
sigh. I have nothing exciting to report on Tiger day. I don't have Tiger on order, nor have I had access to any developer seeds. I'm not going to any Tiger parties, and I'm not doing any special Tiger rituals. </p> <p> I hear that FuzzMeasure runs...