Hi bogusbishop, thanks for reporting this bug. The newest version (0.1.1) contains a fix for the issue.
