Actually, this bug was fixed in rev 120 but a release containing it has not yet been done. I'll prepare a 0.2.5 release shortly.
Actually, this bug was fixed in rev 120 but a release containing it has not yet been done. I'll prepare a 0.2.5 release shortly.