I have observed the snapshot shared by you. I would like to share that you may please use Aspose.Slides for Java 2.4.0. It is the latest version of product at the moment. Please also share the source presentation with us along with possible code snippet that you are using with source presentation, so that we may reproduce and resolve the issue.
PowerPoint 2010 has Trouble recognizing the .PPT and .PPTX files we generate with our code.
This is what I did to test the process:
A. I built a Test .PPT file and a Test .PPTX file on server from "CLONED" slides from other PPT and PPTX files.
B. The saved files were stored on my server. and I downloaded and opened each file in PowerPoint 2007 and PowerPoint 2003. Both Files OPENED FINE with no problems...
C. I then downloaded the Test PPT and PPTX files and opened them with PowerPoint 2010.
D. The Attached Screenshots show you what I see when I open each in PowerPoint 2010.
E. I disabled "Trust Settings" in PowerPoint 2010.
Is Aspose.Slides.Java not yet fully compatible with PowerPoint 2010?
I have observed the issue shared in the PDF file. In order to investigate and resolve the issue, I request you to please share the source presentations along with code snippet. Secondly, an issue with ID 22265 has already been created in our issue tracking system to resolve the issue of error message “PowerPoint found content in presentation that it did not understand” for PPTX file**.** I have associated this thread with mentioned issue but I would still request you to please share the PPTX and PPT files. The support for PowerPoint 2010 is available for both PPTX and PPT presentations. We are also continuously improving our product based on customer feedbacks.
You may please follow the guidelines mentioned here to share the mentioned presentation and code snippet with us. Please notify us in the forum, when you have shared the data via private message.
We are also seeing the red “Protected View” bar in PowerPoint 2010 when opening PPT files generated by Aspose.Slides .NET version 4.4.0. It appears that a similar issue was recently fixed in Aspose.Cells. Hopefully a similar fix can be applied here!
Thanks for the shared suggestion as we get reference from it for issue resolution.Our development team is working on the issue and as soon as the issue is resolved, we will be obliged to share the information with you.