Thank you, @Astrotronic - this will be fixed in the next update, scheduled for April 22. Thank you for the report!