I can't seem to reproduce that bug in the latest release (1.0.3). Were there some other things that you did that might have led to you experiencing the error?
