Add more Properties Methods in StructuredDocumentTagRangeStart Class | Insert Ranged Multi-Sections Content Control in Word Document C# Java

Thank you for starting supporting Section Breaks, I checked the latest API documentation released.

There are few properties missing, if supported then StructuredDocumentTagRangeStart useful.
e.g.

  • Color
  • ChildNodes
  • LockContents
  • LockContentControl
  • Tag
  • GetChildNodes()
  • LastOrDefault()
  • LastChild
  • Placeholder
  • PlaceholderName
  • Title
  • RemoveSelfOnly()
  • RemoveAllChildren()
  • AppendChild()
  • IsShowingPlaceholderText

Could you please let us know if it is going to be supported in feature release or not? It will be helpful to plan some of the development activities.

@GZaha,

We have logged your requirement in our issue tracking system. Your ticket number is WORDSNET-21246. We will further look into the details of this requirement and will keep you updated on the status of the linked issue.

@GZaha,

We will be going to add almost all features to StructuredDocumentTagRangeStart node. There is one important thing though, StructuredDocumentRangeStart node (as well as StructuredDocumentTagRangeEnd node) is essentially not a composite node. Content is not represented by child nodes, it is represented by nodes between range start/end (it’s rather sibling nodes). We are going to implement some helper methods too to make range nodes more useful.

Can you please share with us which feature(s) are most important for your needs? This information can help us with feature scheduling.

@awais.hafeez
Last time I did the same analysis and added the list. All listed api and related features are required. However, it would be helpful to support this as Composite node. This is going to impact huge on our utility to support section break.

Major impact would be scanning for StructuredDocumentTag and then again for StructuredDocumentRangeStart and End node. This will lead into performance impact.

@GZaha,

We have logged your concerns in our issue tracking system and will keep you posted here on any further updates.

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