Aspose changed the property of buttons for Object positioning automically

It seems there is an issue with Object positioning property of buttons.

I created an empty xlsx file and then insert a new button into an empty sheet.
right-click the button and select the item "Format Control", and then select Properties tab.
You will see the default option for Object positioning is "Move but don't size with cells".
now change the option to the first one "Move and size with cells". save the file.

The input file is ready now. You can get it from attachments as well. It is called "Book1.xlsx".

Then execute the code below.
First of all, read the input file into a stream and then save the stream into another new file with aspose.

class Program
{
static void Main(string[] args)
{
string fileName = Path.Combine(System.IO.Path.GetTempPath(), "Book1.xlsx");
byte[] sptStream = null;
//get the file into stream
using (FileStream fileStream = new FileStream(fileName, FileMode.Open, FileAccess.Read))
{
int length = (int)fileStream.Length;
sptStream = new byte[length];
fileStream.Read(sptStream, 0, length);
fileStream.Close();
}

//save the stream into another file with Aspose
using (MemoryStream msSPT = new MemoryStream(sptStream))
{
Aspose.Cells.License license = new Aspose.Cells.License();
license.SetLicense("Aspose.Total.lic");

Workbook wbook = new Workbook(msSPT);
wbook.Save(Path.Combine(System.IO.Path.GetTempPath(), "Book2.xlsx"));
}

}
}

after the Book2.xlsx was generated. open it. you will find the Object positioning of the button has been changed from "Move and size with cells" to "Move but don't size with cells" somehow. It is very strange. This is the issue. Book2.xlsx has been attached.

But if I selected the option 2 or 3 in Book1.xlsx, the option can be persisted from Book2.xlsx. I tried this.

I am using the version 8.9.1.0. but it works fine in the version 8.3.2.1 just before we upgraded the controls. So I am assuming that the upgrade of the controls caused this issue.

Would you team fix this issue? Or could you provide a workaround for now?

thanks,

Hi Andrew,


Thank you for contacting Aspose support, and welcome to Aspose.Cells support forum.

We have evaluated the presented scenario against the latest version of Aspose.Cells for .NET 9.0.7, and we are able to notice the said problem. Moreover, we have performed the same test against Aspose.Cells for .NET 8.3.2 to get correct results. In order to further investigate the matter, we have raised this incident as a Regression in our database under the ticket CELLSNET-44791. Please spare us little time to properly analyze the case and revert back with updates in this regard.

Thanks for your prompt response.
We are looking forward to your updates.

Hi again,


Please try the latest version of Aspose.Cells for .NET 9.0.9 against the problem logged earlier as CELLSNET-44791.

Thanks for your feedbacks.


the latest version of Aspose.Cells for .NET 9.0.9 fixed our issue.

the functionality is back again.

Hi Andrew,


Thank you for the confirmation. It is good to know that you are up & running again. Please feel free to contact us back in case you need our further assistance with Aspose APIs.

Another question.

when do your team plan to release the latest version of Aspose.Cells for .NET 9.0.9?

I can not find it from Aspose.Cells Product Family on your forum. the latest one on the forum I can find is Aspose.Cells for .NET 9.0.0.

Hi,


Well, you may use the fix/version (v9.0.9.x) as an official release of the product for production server, it contains all the features, fixes and enhancements full fledged. We are scheduled to release our next official version of the product, (it might be: Aspose.Cells for .NET v9.1.0) in the third or fourth week of October 2016 (The date is not finalized though). This fix will also be included in the official release of the product (in the Downloads section). Generally we provide fixes (hot fixes) in the forums for the users every week while we publish official release of the product in Downloads module once per month.

Thank you.

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


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