Just a week after releasing 2.0, we are releasing 2.0.1. The primary reason we are doing this is that we received a ton of bug reports about people getting error messages continually when the app started. It turns out that this was due to a conflict that arose when users had some odd combination of accessibility settings set in Mac OS X. No one in the beta test program apparently had these settings, but a number of Mac users do.
The settings are not something you would commonly have turned on; most reporters we talked to, in fact, said they had things set that way by mistake. So I suppose that is why we did not catch it. Still, this tells me we need to improve our practices with our beta program. Continually improving the processes that drive our business is something we have done constantly since I came to Nisus and it is something we will do again, this time with our beta testing.
Now we are turning our attention to speeding up file open times.
2.0.1 SOUNDS beautiful. Gratulations! Very quick response to so many users, I am impressed!
How, where and when can we download 2.0.1.??
Untill now we are redirected from 2.0.1 towards 2.0
henk de weijer
I believe that the accessibility settings that you refer to are those that enable input methods used by Spell Catcher X, Grammarian Pro X and others. Nisus Express has not interacted well with Spell Catcher X since version 1.1. Now with 2.0.1 the interaction problems seem to be fixed. So I wonder if this was a problem that was not unknown but just ignored until the reporting feature in 2.0 unexpected caused a problem that had to be dealt with.
Well, I’m certainly glad to hear the problems with Spell Catcher and Grammarian seem to be resolved! We have looked at this issue but had not been able to resolve it yet.
I’m not sure how the fix for the accessibility conflict would have affected this. The problem in 2.0 was that an error reporting system we added was catching errors generated by Apple’s accessibility system and reporting them. It turns out these Apple-generated errors are “normal” and are not really errors at all. Our fix was to merely turn off the error reporting we had added in 2.0 for Apple-generated errors.
-Charles