Secondary x-axis automatically turned and set to "Custom"

I am testing Aspose.Slides versin 4.1.1.0 and Aspose.Cells version 4.9.0.0



I have some power point slides with embedded Excel data and charts.

I use “smart markers” to inject data into the embedded excel worksheets.



It appears the new version automatically sets the Secondary Axis to
“Custom” even though I have “None” selected in my template file. The
end result is that Aspose always creates a chart with a line (the
secondary x-axis) near the top of the chart which can run across labels
and legends. I do not want the secondary x-axis to show up.



I do not have this problem with older versions of Cells and Slides.



I am not sure if this problem resides in Aspose.Slides or Aspose.Cells.



Attached is a ppt slide showing the secondary axis turned on.



NOTE: I am using office 2003.

Hi,

We will soon look into your issue and get back to you soon.

Your issue has been logged into our issue tracking system with an issue id: CELLSNET-16589.

Thank you.

Hi,

Please try the attached version,

We have fixed the secondary value axis issue.

Kindly let us know if it works fine now.

Thank you.

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


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

While trying to keep the API as straightforward and clear as possible, we have decided to recognize and honor the common development practices of the platform; we have re-arranged API Structure/ Namespaces.

With this release, we have reorganized the API classes for Aspose.Cells component. This change has some major aspects that we follow. We have added new namespaces. The entire API (classes, interfaces, enumerations, structures etc.) were previously located in the Aspose.Cells namespace. Now, certain sets of API have been moved to their relative namespaces, which make the relationship of classes (with their members) and namespaces clear and simplified. It is to be noted here, we have not renamed existing API (classes, enumerations etc.) but, I am afraid you still need to make certain adjustments in your existing projects accordingly.

For complete reference, please see the product's API Reference.
(1)