@sambauers
16 years, 10 months ago
This should not be the case. I’ve isolated a bug that is causing this to happen. Looks like we are going to get a 1.0.1 release sooner rather than later!
