IMAGES versus SHAPES - Aspose treats all as SHAPE

Hi there,
You treat Shapes as Images and there are some Shape properties which are not meant for IMAGES. Aspose throw some silly exceptions like NPE and ClassCastException.

Two ways to handle this at our end:

  1. Provide us the list of all Shape properties not meant for IMAGES, so that we can use Shape.isImage() property to adjust the flow.

  2. Handle it on your end and throw some good exceptions.

We can’t wait for your new version right now that would have fixes for it probably. You can add a ticket for that.

We want something for now. So it would be helpful to tell us the way to avoid NPE and ClassCastException and, **we need list of all Shape’s class APIs (attributes/ properties), that would throw exceptions and not meant for image?

Is there any other thing like IMAGE for which Shape.Properties will throw exceptions?**

We don’t want to catch and handle silly exceptions like NPE and ClassCastExceptions, and please provide us better way.

I also discussed with Awais that you guys should be covering things like this in your unit test cases, so that it would not create a problem when upgrading to new version of Aspose.

Any help would be appreciated.

Thanks,
Prakhar
.

Hi Prakhar,

Thanks for your inquiry. This was one of the issues that slipped into the release after big DrawingML rework we have done. It is fixed already as per WORDSNET-11813 and will be live with the next release i.e. 15.5.0. We will inform you via this thread as soon as 15.5.0 release is published at the start of June 2015. We apologize for any inconvenience.

Best regards,

The issues you have found earlier (filed as WORDSNET-11813) have been fixed in this .NET update and this Java update.

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

The issues you have found earlier (filed as ) have been fixed in this Aspose.Words for .NET 18.12 update and this Aspose.Words for Java 18.12 update.