Thanks for the bug report! I would assume so, since I caught a similar bug recently in a development build. Luckily, I'm about to release an update tomorrow that will fix it!
