>>656
That bug is fixed now. Please let me know if it reoccurs.