Thanks for the heads up - that's largely fixed in the next update I'm planning to release in another week or so.
