@ Roger Nifle
Thanks for reporting this bug. I’ll be pushing out an update this weekend which fixes this error. There version to look for will be 0.7.6.2.