Image Contrast not preserved when rendering image from excel

Hi,

I the excel file (image_contrast.xlsx) I have an image with
low contrast set. Rendering the file content with the image as a
image losses the contrast setting. (see image_contrast.xlsx.out.png file)

The code used to obtain the image file is :

const string filePath = @“C:\image_contrast.xlsx”;

var workbook = new Workbook(filePath);

var imageOptions = new ImageOrPrintOptions
{
Quality = 100,
VerticalResolution = 200,
HorizontalResolution = 200,
PrintingPage = PrintingPageType.IgnoreBlank,
ImageFormat = ImageFormat.Png,
OnePagePerSheet = true
};

var worksheet = workbook.Worksheets[0];

string printArea = string.Format(“B3:T45”);
worksheet.PageSetup.PrintArea = printArea;
worksheet.PageSetup.TopMargin = 0;
worksheet.PageSetup.LeftMargin = 0;
worksheet.PageSetup.RightMargin = 0;
worksheet.PageSetup.BottomMargin = 0;

var sheetRender = new SheetRender(worksheet, imageOptions);

sheetRender.ToImage(0, filePath + “.out.png”);

Thank you,
Lucian Nistor

Hi,

Thanks for your posting and using Aspose.Cells.

After initial investigation, we have found this issue. The image contrast is not preserved in the output image.

We have logged this issue in our database. We will look into it and fix it. Once the issue is fixed or we have some other update for you, we will let you know asap.

This issue has been logged as CELLSNET-41576.

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


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

I’ve tried with Cells 7.3.4.1 and the problem isn’t fixed.
The steps to reproduce remain the same.

Regards,
Lucian Nistor

Hi,

Thanks for your posting and using Aspose.Cells.

We were able to replicate this issue with the latest version. We have logged your comments in our database. We will look into your issue and resolve it. Once, we will have some update for you, we will let you know asap.

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