.SaveAsEMF vs Save(ImageFormat.Emf)

Aspose.BarCode Product Family
1

I see that the BarCode-toolkit now save real EMF-files, but the artwork-dimensions does not seem to be correct.

If I save the QR-barcode using

.Save("c:\temp\test.emf",ImageFormat.EMF)

the resulting file (png I know), will have dimensions 574x574

If I save the same barcode

using

.SaveAsEMF("c:\temp\test2.emf")

the resulting file (real emf-file), will have the dimensions 1626x1629, where the actual QR-code is placed in the top left corner of the image with real dimensions 431x431. In other words, there is a lot of space around the QR!

Another question is that I'm missing the SaveAsEMF that save to a stream and not just to file.

2

Hi,


Thank you for inquiry.

.SaveAsEMF() method will save the image in real EMF format (vector graphics). I have also seen the extra space when I generate a QR barcode using this method. I have also logged this issue (ID: 31903), we will look into it and will inform you when it gets fixed.

.Save("a.emf, ImageFormat.emf) actually saves to default PNG format (raster graphics), so please use SaveAsEMF() method to get the pure vector graphics image.
3

What about saving emf to a stream and not just a file?

4

No progress yet?

5

Hi,


I am afraid, I do not have any updates regarding this issue. Although I have requested for the ETA and as soon as I receive any updates, I will post here for your reference.
6

The issues you have found earlier (filed as 31903;33020) have been fixed in this update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
7

Hi,


You can now save the EMF file to stream. Please check the below source code for your reference,

C#
var stream = new MemoryStream();
builder.SaveAsEmf(stream);
8

Does not appear to be working as intended ? (unless having a valid license changes the way it is working).

I've generated the same content into a PNG-file and an EMF-file. The size is not the same for these two files (attached).

I'm also noticing that I'm unable to open the .emf-file in Adobe Illustrator (which actually was working previously).

9

Hi,


Thank you for your patience and your feedback.

I have noticed the the extra space around the image is reduced but the barcode label itself isn’t centred. That is why when you hide the captions the barcode label seems to be cropped from upper-left side. I have re-opened the associated ticket by attaching your feedback with it.

We will look into this matter very soon.

Regards,
10

Any progress???

11

Hi,


I am afraid, I do not have any updates regarding the issue of extra space around the EMF image. I have requested for the ETA and as soon as I receive any updates, I will post here for your reference
12

Still not got a fix for this?

13

Hi,


We are really sorry for this delay.

I just got to know that the issue hasn’t been fixed yet, otherwise we would have provided you a hotfix version. I am in direct contact with the development team to include this fix in the upcoming release of Aspose.BarCode for .NET, that is scheduled for the following week.
14

4+ months and still not fixed???

15

Hi,


We are sorry for your inconvenience and the delay.

I have checked the status of the ticket (BARCODENET-31903) and I can see that the development team has scheduled the fix for the upcoming release of Aspose.BarCode for .NET v4.7.0. The said release will be published in first half of the following month (April).

We will notify you once the issue is resolved and the fix is available for public use.
16

But it did not make it to this release?

17

Hi Stein,


We are extremely sorry for all the troubles.

I am afraid, yes. Your posted issue was not fixed in time, therefore it couldn’t make it to the v4.7.0 release of Aspose.BarCode for .NET. Upon checking the current status of the ticket BARCODENET-31903, I can see that the issue is fixed now, and we will provide the fix with upcoming release of Aspose.BarCode for .NET v4.8.0.

Many thanks for your patience.
18

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

This message was posted using Notification2Forum from Downloads module by aspose.notifier.