We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

1200 DPI Resolution not using BarHeight properly

With v7.2, using a Resolution of 1200DPI results in barcodes where the BarHeight property is not being used properly:



BarCodeBuilder b = new BarCodeBuilder("(01)90013670000396(3200)15(11)150819");

b.AutoSize = true;

b.SymbologyType = Symbology.GS1Code128;

b.CodeTextFont = new Font(“OCR B Std”, 10.0f);

b.GraphicsUnit = GraphicsUnit.Millimeter;

b.xDimension = 0.495f;

b.BarHeight = 31.75f;

b.CodeTextSpace = 0.5f;

b.Resolution = new Resolution(1200.0f, 1200.0f, ResolutionMode.Customized);

b.Save(“GS1Code128 Sample at 1200dpi.png”, BarCodeImageFormat.Png);



The attached samples are for 300 and 1200 DPI. The 300 DPI sample correctly renders a barcode with a bar height of 31.75mm. The 1200 DPI sample results in a barcode with a bar height of 21mm, which is below the minimum standard for this barcode.



What I have found is ALL barcodes in the set I am using (DataBarStackedOmniDirectional, GS1Code128, UPCA, ITF14) have this issue, no matter what the BarHeight is set to. I tried 45.0f, and that still resulted in 21mm barcode.

Hi Tony,


Thank you for contacting support. We have tested these use cases and logged investigations as follows:

BARCODENET-34280 - GS1Code128 Encoding, BarCodeBuilder.BarHeight properly does not work properly
BARCODENET-34281 - DataBarStackedOmniDirectional encoding, BarCodeBuilder.BarHeight properly does not work properly
BARCODENET-34282 - UPCA encoding, BarCodeBuilder.BarHeight properly does not work properly
BARCODENET-34283 - ITF14 encoding, BarCodeBuilder.BarHeight properly does not work properly

Your post has also been linked to these ticket ids. We’ll let you know once a significant progress has been made in this regard. We’re sorry for the inconvenience caused.

Hi Tony,

Thank you for being patient. We have a good news for you that the issue ids BARCODENET-34280 and BARCODENET-34282 have now been resolved. If there is no issue in the QA phase, then their fixes will be included in the next version of Aspose.BarCode for .NET 7.4.0. We'll inform you via this forum thread as soon as the new release is published.

Thanks! Can I get a status check on the other 2 issues that are covered in this forum thread? BARCODENET-34281 and BARCODENET-34283. Having all 4 fixed in time for the v7.4 release is rather critical to the software project I have in progress.



Also, I do want to make sure the changes are also reflected when using SaveAsEmf to save out the Barcode. The example I gave was for PNG, but I imagine it affects EMF format as well.

Hi Tony,

All four issues including BARCODENET-34281 and BARCODENET-34283 have been resolved and are in review phase. These fixes will be part of 7.4.0 release. You will be updated as soon as 7.4.0 version is released.

Best Regards,

I see that v7.4 was released as a Nuget package. I do not believe BARCODENET-34281 was properly resolved. That bug fix was for the DataBarStackedOmniDirectional. The other 3 issues do look perfect.



For some xDimension/BarHeight combinations, the BarHeight is not what is being requested. I have examples that do work properly, but for the ones below, it does not make sense the requested BarHeight would not be accurately used. That should be universally accurate.



(all values are in mm – My actual measurements can’t get any finer than a tenth of a decimal)

xDim: 0.264, BarHeight: 18.22 --> Gives an actual BarHeight of 18.0

xDim: 0.264, BarHeight: 18.24 --> Gives an actual BarHeight of 18.0

xDim: 0.330, BarHeight: 27.77 --> Gives an actual BarHeight of 27.4

xDim: 0.330, BarHeight: 27.78 --> Gives an actual BarHeight of 28.2

xDim: 0.495, BarHeight: 34.16 --> Gives an actual BarHeight of 34.5

xDim: 0.660, BarHeight: 45.54 --> Gives an actual BarHeight of 45.2

xDim: 0.660, BarHeight: 62.70 --> Gives an actual BarHeight of 62.1



Can this issue either remain open, or another one opened to resolve this issue?

The issues you have found earlier (filed as BARCODENET-34283;BARCODENET-34282;BARCODENET-34280;BARCODENET-34281) have been fixed in this update.


This message was posted using Notification2Forum from Downloads module by Aspose Notifier.

Just making sure this is seen, that I do not consider BARCODENET-34281 as resolved.

Hi Tony,

We are in communication with our product team on this issue and will share more detail with your soon.

Best Regards,

Hi Tony,

A new issue to completely fix BARCODENET-34281 against all combinations has been logged into our issue tracking system as BARCODENET-34319. We will keep you updated on this issue in this thread.

Sorry for the inconvenience.

Best Regards,

The issues you have found earlier (filed as BARCODENET-34319) have been fixed in this update.


This message was posted using Notification2Forum from Downloads module by Aspose Notifier.