MoveTo Class
Move Destination Paragraph.When the object is serialized out as xml, its qualified name is w:moveTo.
Inheritance Hierarchy
System.Object
DocumentFormat.OpenXml.OpenXmlElement
DocumentFormat.OpenXml.OpenXmlLeafElement
DocumentFormat.OpenXml.Wordprocessing.TrackChangeType
DocumentFormat.OpenXml.Wordprocessing.MoveTo
Namespace: DocumentFormat.OpenXml.Wordprocessing
Assembly: DocumentFormat.OpenXml (in DocumentFormat.OpenXml.dll)
Syntax
'Declaration
Public Class MoveTo _
Inherits TrackChangeType
'Usage
Dim instance As MoveTo
public class MoveTo : TrackChangeType
Remarks
[ISO/IEC 29500-1 1st Edition]
17.13.2.26 moveTo (Move Destination Paragraph)
This element specifies that the parent paragraph has been moved to this location and tracked as a revision. This does not imply anything about the revision state of the contents of the paragraph, and applies only to the existence of the paragraph as its own unique paragraph.
The following restrictions shall be applied to this content:
- If this element occurs outside of a move destination container (§17.13.5.28; §17.13.5.27) for which a matching move source container (§17.13.5.24; §17.13.5.23) exists in the document, then the document is non-conformant.
[Example: Consider a WordprocessingML document in which a paragraph of text is moved down in the document. This moved paragraph would be represented using the following WordprocessingML markup:
<w:moveToRangeStart w:id="0" w:name="aMove"/> <w:p> <w:pPr> <w:rPr> <w:moveTo w:id="1" … /> </w:rPr> </w:pPr> … </w:p> </w:moveToRangeEnd w:id="0"/>
The moveTo element as a child of the run properties of the paragraph mark specify that this paragraph mark was part of the content which was moved in the document. This implies nothing about the contents, since they might have been added later and not tracked as a revision (they must be marked as a move using the moveTo element (§17.13.5.25) around the run content). end example]
Parent Elements |
|---|
rPr (§17.3.1.29); rPr (§17.3.1.30) |
Attributes |
Description |
|---|---|
author (Annotation Author) |
Specifies the author for an annotation within a WordprocessingML document. If this attribute is omitted, then no author shall be associated with the parent annotation type. [Example: Consider a comment represented using the following WordprocessingML fragment: <… w:id="1" w:author="Example Author"> … </…> The author attribute specifies that the author of the current annotation is Example Author, which can be used as desired. end example] The possible values for this attribute are defined by the ST_String simple type (§22.9.2.13). |
date (Annotation Date) |
Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of ISO/IEC 29500. If this attribute is omitted, then no date information shall be associated with the parent annotation type. [Example: Consider a comment represented using the following WordprocessingML fragment: <… w:id="1" w:date="2006-01-01T10:00:00"> … </…> The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which can be used as desired. end example] The possible values for this attribute are defined by the ST_DateTime simple type (§17.18.9). |
id (Annotation Identifier) |
Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element. If this attribute is omitted, then the document is non-conformant. [Example: Consider an annotation represented using the following WordprocessingML fragment: <… w:id="1" … > … </…> The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example] The possible values for this attribute are defined by the ST_DecimalNumber simple type (§17.18.10). |
[Note: The W3C XML Schema definition of this element’s content model (CT_TrackChange) is located in §A.1. end note]
© ISO/IEC29500: 2008.
Thread Safety
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.