Fixed a erroneous message stating that 1D results have not been saved even if they have been actually saved to disk.
Fixed some utilization percent (by dividing the result by 100).
Fixed a erroneous message stating that 1D results have not been saved even if they have been actually saved to disk.
Fixed some utilization percent (by dividing the result by 100).
Pieces are draw with real height when the angles are different from 90.
If the angles are 90, and heights are greater than 0, the user can force the drawing with fixed height from Results | Additional | Draw the pieces with a fixed height menu.
Fixed a bug where values for angles were not validated while manually entered in the Parts table. Valid values for angles are between 0 and 180 degrees.
Fixed a bug where UI settings were loaded from a project file when the project was imported. This behavior was not intended.
Fixed a bug (introduced in 5.18.10.2) that prevented Parts from being saved to XML files.
Fixed some toolbar buttons whose width does not accommodate with text inside them.
Fixed some too long translation texts.
Current date can be printed on Stock adhesive labels.
Fixed crash when all 1D parts length are longer than the 1D stock lengths.
Project button has been moved after the Settings button in the main toolbar.
Fixed a bug which can crashes the program if all Parts are longer than the largest Stock length.
Width column is not visible in Statistics for 1D Results since the width of 1D pieces is always 0 (otherwise is considered as being a rectangular piece).
Adding a product to Parts is done directly from the Products window by pressing the OK & Add to Parts button. The old submenu from Products menu has been removed.
The added product can be previewed in the Product – add to Parts window which shows the list of sizes and the new names for materials and edge bands.
Fixed crash when all 1D parts length are longer than the 1D stock lengths.
Many internal updates of code to allow easier development in the future.
We have limited the quantity of Stock pieces to 1 million per row. We did this because it is enough for the 99.99% of cases that the program is intended to handle. Also, larger quantities can lead to the crash of the application which is a 32 bit application and cannot access more than 2GB of RAM.