Ben,

Yes, this bug (1413) was fixed in version 1.3b3.
Thanks for checking back,

Cam

Reply via email to