Hmmm...I haven't been able to reproduce that error after posting the update last evening. I'll give it some more research and see if I can track it down.
