This completely flew under my radar. Sorry about that.
A couple of the latest (1.2) updates should've fixed this. If similar behaviour still occurs, let me know and I'll investigate it.
