Hey, this issue has already been fixed on my development version--the next time I release an update it will be sorted!Thanks for reporting.
