Thanks for reporting this.. this was already logged and will be fixed in next rev..