It might not be completely fixed...
With 2.0.7 the failure occurred every time. But with the 2.0.8 beta, I have now seen the problem occur once after about half an hour of use. After quitting and restarting it seems ok again and I can not repeat the failure - if I can find exactly what provoked it I will post again.
It might not be completely
It might not be completely fixed...
With 2.0.7 the failure occurred every time. But with the 2.0.8 beta, I have now seen the problem occur once after about half an hour of use. After quitting and restarting it seems ok again and I can not repeat the failure - if I can find exactly what provoked it I will post again.