I have started adding some short feature guides to the wiki to smooth things over until I finish working on the help PDF. Look through them and let me know where any information needs to get added. </p> Check out the FuzzMeasure Guides here.
I got the last new feature in for 1.3, and you can find the link to 1.3b2 below. If you notice anything odd, please email fuzzmeasure@supermegaultragroovy.com as usual. </p> <p> Get FuzzMeasure 1.3b2 now! </p> <p> No new features will go into this...
I have one last feature to implement before I can bless FuzzMeasure for external release! Luckily, it should not take too long to finish, as I usually save the easiest features for last. </p> <p> As with everything else, it'll take longer than I plan...
Sorry about the lack of updates. I have spent the majority of my free time hacking away on 1.3. Some extra features got into the mix, and I have more ideas about how to present the correction features to the user. Unfortunately, the best ideas about...
I promised to give an update about what I did all the extra coding for. First, some background. </p> <p> I spent the last two weeks on vacation – far away from my home. This fact helps explain why the big outage affected me for a few days rather...
Hopefully the big outage that hit supermegaultragroovy.com these last few days didn't affect anyone too badly. I didn't get any purchases during the outage, so nobody got stuck waiting for my server to issue license keys. I fear that people may have...
"If I do not hear about any issues over the next week…" </p> <p> It does not take long for someone to figure out that electrical measurements got screwed up. Avoid beta 1 for now. I have the problem 99% solved and plan to put a build up soon. :...
I spent quite a bit of time debugging the registration process users go through when they purchase FuzzMeasure. In the current situation, I mail users a standard plaintext email that contains a (pretty long) key that the user must copy & paste into...