Thanks Levi, I've figured out what was wrong and fixed this in 4.0.2 released today :-) Thanks for raising this
