Shhh, we're hunting bugs
But you are thinking "It's wabbit season". Golden age cartoon references aside, this morning we discovered a very unexpected bug in Listz under 10.5 release. Listz will consume 100% of the processor resources (only on 10.5 release). It did not show up under any of the pre-release developer versions we were working with so it may take us a couple of days to find it and squash it. However, we are on the job and working hard. We will post a fix as soon as possible. There should be no risk to your data or your system, Listz will just hog all the processor resources while it is open. Until we post a fix you can continue to use Listz, just quit any other applications until you are finished, then re-open them when you have quit out of Listz.
One of our incredible users (and we have flat-out have the coolest users around) discovered another bug which we have already corrected. If you change an item in an auto-generated tab, like Due Today, Due Tomorrow, or ALL, in a List that has another open window, the change is not properly updating in the other window. If you close the list and re-open it the update will display properly. This is a bug and we have a fix for it that we will release when we get the processor-hogging problem resolved.
I will keep you posted on our progress.
Until then, all the best from us!
One of our incredible users (and we have flat-out have the coolest users around) discovered another bug which we have already corrected. If you change an item in an auto-generated tab, like Due Today, Due Tomorrow, or ALL, in a List that has another open window, the change is not properly updating in the other window. If you close the list and re-open it the update will display properly. This is a bug and we have a fix for it that we will release when we get the processor-hogging problem resolved.
I will keep you posted on our progress.
Until then, all the best from us!

0 Comments:
Post a Comment
<< Home