We've fixed this in 1.1, Rob. It wasn't really a one-line fix of any sort, so it didn't make it into 1.03.

Peter