It seems that in the 'Cloth Count' section of the File Properties dialog the units are fixed and cannot be changed. Even if the in the Configure dialog the Cloth count units are changed from the default cm to Inches the file properties dialog will always show cm Reproducible: Create a new project with the default settings (Configure dialog pattern units set to cm. Start work on project. Open the File properties dialog notice the cloth count is set to units/cm. Go into settings > configure kxstitch, in the pattern options change the cloth count units to inches and apply. Check the File properties dialog and notice the cloth count is still measured in units/cm rather than units/in.
The configuration dialog affects new patterns only. If you change settings there, then do File->New, you will see the settings reflected in the new pattern. The file properties dialog relates to the currently active pattern. If configuration options were applied to the currently active pattern, it may have adverse effects, so it is not done. If there is a need to change the units for the cloth count of the existing file, I can look at implementing the same method used in the configuration dialog within the file properties dialog.
Thanks for the information. I have worked around the issue by copying the pattern to a newly created pattern with the correct cloth count settings (I assume this so have no adverse affect?) It was not obvious to me that the cloth count could not be changed (I'm migrating some patterns) or how it could have an adverse affect. As a feature request I'd like to suggest that when creating a new pattern the user is prompted/notified that the pattern will created with certain options that cannot be changed (eg cloth count) or alternatively, have empty pattern template choice similar to how Microsoft word has a selection of templates (CV, letter, report etc) Where the cloth count, size etc could be saved as a template. Thanks for the quick response and your work on KXStitch (Happy for this to be closed out as not a bug)
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.