This has been fixed as part of the next Touch 2.0 release. Thanks for the report.