Dear Customers,
We have released Aspose.Slides for Java 1.7.0.0.
This release includes changes made in 1.6.* hot fixes and new features:
New: Read/write access to HeaderFooter properties. New: Reading non-msoffice OLE objects. For example reading embedded PDF documents. New: Reading PDF (and other non-MS) OLE objects. Fixed: Correct recognizing embedded Controls as OleObjectFrame. Fixed: Deleting rows and columns which contain merged cells. Changed: Tables and images optimized by speed and memory.
Aspose.Slides for Java 1.6.17.0 released!
Hot fix contains:
Fixed: Reading presentations with shape coordinates saved in “non standard” way. Fixed: Reading formatted text. In last few hot fixes some portions of formatted text were not readable.
Aspose.Slides for .NET 2.6.15.0 released!
Hot fix contains:
Fixed: Reading ppt files where shape’s coordinates saved in non-standard way. Fixed: Deleting rows and columns which contain merged cells.
Aspose.Slides for .NET 2.6.14.0 released!
Hot fix contains:
New: Reading PDF (and other non-MS) OLE objects created as Icon.
Aspose.Slides for .NET 2.6.13.0 released!
Dear Customers,
Unfortunately, our 2.6.11 and 2.6.12 fixes were unstable because of too heavy optimization.
New 2.6.13 version should work fine and also contains all features added in 2.6.11 hot fix.
Aspose.Slides for .NET 2.6.12.0 released!
Hot fix contains:
Fixed: Slides.AddOleObjectFrame could throw NullReferenceException. This bug exists in the 2.6.11 version only.
Aspose.Slides for .NET 2.6.11.0 released!
Hot fix contains:
New: Reading non-msoffice OLE objects. For example reading embedded PDF documents. Fixed: Correct recognizing embedded Controls as OleObjectFrame.
Aspose.Slides for .NET 2.6.10.0 released!
Hot fix contains:
Memory optimization on loading images and rendering of slides.
Aspose.Slides for .NET 2.6.9.0 released!
Hot fix contains:
Fixed: Slide.ChangeMaster could generate wrong slides which are not readable later by Aspose.Slides.
Aspose.Slides for .NET 2.6.8.0 released!
Hot fix contains:
Fixed: GetThumbnail could throw exception “-2147483648 is not a valid value…”.