LayoutTableRowsApart Class
Allow Table Rows to Wrap Inline Objects Independently.When the object is serialized out as xml, its qualified name is w:layoutTableRowsApart.
Inheritance Hierarchy
System.Object
DocumentFormat.OpenXml.OpenXmlElement
DocumentFormat.OpenXml.OpenXmlLeafElement
DocumentFormat.OpenXml.Wordprocessing.OnOffType
DocumentFormat.OpenXml.Wordprocessing.LayoutTableRowsApart
Namespace: DocumentFormat.OpenXml.Wordprocessing
Assembly: DocumentFormat.OpenXml (in DocumentFormat.OpenXml.dll)
Syntax
'Declaration
Public Class LayoutTableRowsApart _
Inherits OnOffType
'Usage
Dim instance As LayoutTableRowsApart
public class LayoutTableRowsApart : OnOffType
Remarks
[ISO/IEC 29500-1 1st Edition]
9.7.3.24 layoutTableRowsApart (Allow Table Rows to Wrap Inline Objects Independently)
This element specifies whether tables which are wrapping around floating objects shall wrap around the object as a whole, or if each table row shall individually wrap the object as needed (causing a more stuttered, yet tighter, wrapping of the object).
Typically, when a table wraps around a floating object, the table shall wrap the object as a unit (i.e. the whole table square wraps the object). This element, when present with a val attribute value of true (or equivalent), specifies that wrapping is applied to each row in the table one by one, even if its means that each row has a different resulting position with respect to the table.
[Example: Consider a WordprocessingML document with a floating shape using square wrapping.
The default presentation would have the entire table wrapping around that shape:
However, if this compatibility setting is turned on:
<w:compat> <w:layoutTableRowsApart /> </w:compat>
Then each row would wrap around the shape one by one, resulting in the following output:
end example]
Parent Elements |
---|
compat (Part 1, §17.15.1.21) |
This element’s content model is defined by the common boolean property definition in Part 1, §17.17.4.
© 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.