The following release notes apply to Microvellum build 26.1.0723.641.
The Function Arguments interface has received a major visual overhaul to improve the usability, clarity, and visibility of several elements. Input fields are now significantly larger, placed in a more comprehensive layout across 4 distinctly separated cells, result columns in more visible read-only cells, and the function list has been replaced with a more accessible ribbon layout of each function category at the top of the interface. The cell columns are scrollable and adjustable, with the ability to manually adjust the size of all cells simultaneously, ensuring the entered function is always visible and readable and removing the need to make constant adjustments or scroll excessively.
A handful of issues were reported relating to dados.
Users who modified Parameter 1 (Ramp Associative Dado) of dado tokens found that the dados would have all relevant information be affected by the change, including causing an error and failing to produce G-code as intended.
Certain products with dado tokens applied would fail to draw when placed individually, with the names of the rooms the products are placed in displaying as blank in the Product Viewer.
Some users reported an issue wherein certain routes were unable to be machined due to their length, with the Ramp Associative Dado token failing to produce usable G-code.
All these issues have been resolved- the Ramp Associative Dado token should now retain all relevant information, products which were unable to be drawn and had no rooms in the product viewer should now be drawn and display their room names correctly, and shorter routes should now be able to be able to be machined, provided the route lead is at least as long as the radius of the tool bit selected.
Several issues were occurring when creating new G-code.
Users who created new G-code from composite drawings found that the scale of curved shapes (circles, arcs) in their composites were significantly larger than expected, resulting in erroneous G-code.
When editing parts in the composite via Nest Editing Tools to create new G-code, it is sometimes the case that certain parts of the code will erroneously change from the original.
Users who created copies of G-code to modify would sometimes find that certain values would be incorrectly modified without any input, such as tool compensation.
When updating or making new G-code from existing G-code, some users reported an issue wherein nested parts would be erroneously rotated or mirrored.
Certain formats of G-code would sometimes reformat incorrectly when modifying the G-code or creating a copy of it.
All of these issues have been resolved- G-code should now generate correctly, and not have any unprompted changes applied when modifying the drawing, be it via the composite or through manual alteration of the text.
An error was sometimes occurring when attempting to change the saw output type in the Saw Processing Station. This issue has been resolved, and this error should no longer occur.
A change in a recent build set the Parts List UI to prompt users on whether they wished to save the changes they had applied. However, some users reported this prompting would not occur for them when they accessed the Parts List through the Products List, resulting in changes not being saved when the UI was closed.
This issue has been resolved. The prompt to save changes should now occur universally when attempting to close the Parts List, as intended.
It was reported that some users were experiencing an issue when attempting to update G-code of work orders that were primarily comprised of parts with Face 6 machining applied. Users found that updating the G-code of the work order or product would result in the creation of an entirely new folder and file rather than updating the existing one, resulting in some confusion and excessive amounts of file management.
A similar issue was reported wherein updating the G-code would update the existing file properly but also create a new folder with a new batch name, potentially causing confusion.
Both issues have been resolved. The existing file should now be updated, with no new folder being created.
An issue was reported regarding the text color of formulas in the Product Prompts UI. It is expected that formula Prompts will display their text values in red to signify that they are formula driven prompts, but some users found that all prompt values in the UI would display as black, erroneously indicating that they were static values tied to no formulas. This issue has been resolved- the prompt values should appear with the correct red color.