Release Notes for v0.9.1

Translations and Bugfixes

As is the case since the last update - I cannot send bulk emails anymore but you can log into your account at the store and download the newest version without needing an email.

UPDATE: Fixes in v0.9.1.2

• Fix for Linux Black Screen on newer kernels that also works on older kernels.

• Fix for issue with Translations invalidating your Layouts and only working in the Language they were created under. This fix will break any layouts made under a different language but they will now carryover between languages without issue.

• Fix for occasionally deleting the personal_library.json and overwriting with a blank version.

• Fix for missing TD-1 files and it will clear out old files if they exist.

• Fix for version number not including the final .x in the check. It will correctly check for that now and the version number has been updated. However, the old version will not correctly identify an update existing when the release version is longer than the source version, so v0.9.1 or earlier won’t see the new version (but going forward it will)

• Attempted fix for Pla+/PLA+ mismatch when pulling filaments into the merged PLA/PLA+ menu in French with Placeholder Translation.
  

As described in the Known Issues post, v0.9.1 is mostly about Translations and bugfixes for v0.9.0. There are a FEW exceptions and some extra bug fixes

Bug Fixes

• Fix crash on Ctrl+N (New Project) with a layer height of 0.08mm

• Fixed crash when changing Steps in the Blend Assistance without first setting Source and Target Colors

• Fixed MacOS Drag/Drop to not require the release of the Cmd key to drop. FYI this is a MacOS specific issue where it treats a drag with Cmd pressed as being a global drag and pulls it out of the application. I rewrote the entire drag/drop stack to fix things for MacOS. Hopefully I didn’t break anything - I spent a decent amount of time testing this.

New Features

A few new features snuck in but they were, by design, very minimal. These don’t include Translations which are handled in the next section.

• TD-1 (or TD1s) firmware version 2.0.0 included.

• Changed all TD-1 Menus and menu items to TD1

• Fixed the recover TD1 option to work reliably

• Added Release Notes dialog for TD1 firmware updates

• Added “What is TD?” Information pop-up with more details on why TD matters and how to measure it. This will alternate with the HueForge Resources dialog at startup until “Don’t show this again” is checked. This can be accessed through the Help menu or the ? link in the Filament Dialog next to TD afterwards.

• Added the ability to choose to check automatically for updates. This checkbox is in the Help menu and follows the idea of never trying to reach the internet without the user knowing. This will check on HueForge startup once per day. You can still check manually if you want.

HueForge Translation

HueForge will now accept Qt Translation files (.qm files) as well as translated version of html or json files that are in HueForge (like the “What is TD?” dialog contents.) Changing Translations will require a restart of the application (and MacOS will often report that it crashed and restarted as it doesn’t like the quick turnaround) to get everything consistent.

There is a public GitHub repo here with the source files needed for translating HueForge as well as instructions on how to create new files. Translations can be loaded dynamically either through Preferences→Language→Manage Translations or by simply copying them into a folder called translations in your Configuration directory. At launch I have most things translated in French (Thanks to Placeholder and Quasar Creations3D) (More UI elements were added after the initial translation), virtually everything in Japanese due to the help of Daisuke and two other collaborators (please tell me the name you want to go by and I’ll add it here) and Simplified Chinese by Evan76. I have another partial Simplified Chinese translation that will hopefully be updated soon that I can include in the GitHub repo.

If your language isn’t there, it’s because I haven’t made contact with community members able to help with the translation. Machine translations have been VERY poor given the 1-2 word controls and no context. But adding new translations as the community makes them is incredibly easy for end users to do as soon as they are available and you can have multiple translations from different sources for the same language and HueForge will coordinate that and let you pick the one you want.

If you are part of a language community without a translation, it is important to note that you could start with JUST the main controls and work from there slowly updating over time. There is no requirement that all text is fully translated before submitting a new translation file. The overall management of the GitHub repo has not been finalized and I will likely be looking for some community managers to help with this task. Let me know if you are interested.