Okedoke, in that case the most recent build (here) should have that fixed up. Lemme know if the issue persists!
