I noticed two particular behaviors that I would think wrong.
Calculation of column widths changes according to the screen dpi: for example on my 96 dpi screen the StandardWidth and GetColumnWidth(0) gives 8.42… but when switching to 120dpi it gives 8.3333… for the same file.
When executing a line of code that under the hood creates a Column instance, the Width of that column will be serialized into the saved workbook, but with a Math.Floor to 2 digits applied before. This obviously makes the widths different between saves and moreover they are saved inside the document according to the dpi. They should not be saved at all.
For now this bug is not prioritized, but in case we can rise it later.
I will attach an example. It must be run on different screen dpi to see the different effects.
Seems that using CellsHelper.DPI = 96; solves partially the problem (but I really don’t know what will happen when you develop a template on a 120dpi screen and try to manipulate it on a 96dpi screen with Aspose.Cells).
ConsoleApp1.zip (9.1 KB)