Hmmm... question: did anyone fix this? *cough* *cough*
I could not reproduce the problem, no matter what I tried, so I did nothing... :?
Is the bug back if you revert to an older version (just for trying)?
If I revert back to Rev 1493, the bug is still there. You could revert back yourself because when you checked it was a newer version than what I was using to reproduce the bug. Either way, it looks like the bug was fixed in a more recent build. I am upgrading to Rev 1562 today after I type this. Thanks for the good work.
jmccay