Thanks for reporting the issue -- I'm working on a fix for that issue right now, I'm looking to have it resolved for the next update.
