On the heels of v3.80.3 is v3.80.4. This build fixes more pane positioning anomalies that were still present in v3.80.3. Yes, I'm quite embarrassed about this. I never saw them during testing because of the particular way I utilize the Process Lasso GUI. A lot of existing users didn't see the anomalies for the same reason. Sadly, I'm sure many new users of the product did see these child window positioning anomalies. This time it really caught me by surprise.. I thought I had it fixed.
Other than these GUI issues, v3.80 has been really solid. I worked extensively on the core functionality, but clearly faltered in a very visible part of the product - the GUI. Now, its up to me to recover from these non-critical, but important mistakes and continue on with development and life. I'm looking into ways to better my QA so that little user interface bugs don't slip through. I have automated tests for much of the core functionality, but the user interface is less able to be tested in an automated way.
In the end, I encourage my users to always report any anomalies they see. Had a user not been brave enough to report the continuing v3.80.3 GUI anomalies, they might still exist. One of the causes of my failure here may have been that I released v3.80.3 while I was sick, so released it and then didn't get back to my PC for a little while. So, perhaps I would have eventually have noticed it a few days later, but still a user report is what got me on the ball. Once I was aware of the problem, it took less than 10 minutes to fix.
I'm feeling better now, and will resume development work. I can tell you though that the new major version of Process Lasso is going to be delayed a bit, as I continue to polish the v3.80 code. There will probably be several more minor updates to v3.80, none of them critical, but all of them continued incremental improvements to the code.
Thursday, 4 February 2010
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment