Yes, I was just able to find and deal with this error today. The problem was with the saving process. Starting with version 0.1.7 this bug will be fixed.
Cool! Thanks!
