View Single Post
Sorry! This is fixed for 1.0.2. (We didn't quite find the bug in time for it to go into the pending 1.0.1 release.)