NoColumnBalance class

Office 2013 and later

Do Not Balance Text Columns within a Section. When the object is serialized out as xml, its qualified name is w:noColumnBalance.

Namespace:  DocumentFormat.OpenXml.Wordprocessing
Assembly:  DocumentFormat.OpenXml (in DocumentFormat.OpenXml.dll)

public class NoColumnBalance : OnOffType

[ISO/IEC 29500-1 1st Edition]

noColumnBalance (Do Not Balance Text Columns within a Section)

This element specifies whether the contents of sections with multiple columns defined using the cols element (Part 1, §17.6.4) should automatically be balanced. In terms of column layout, balancing is the act of attempting to ensure that the number of lines in each column is equivalent (rather than completely filling one column before populating the next).

Typically, column balancing is automatically performed on the contents of sections with multiple columns. This element, when present with a val attribute value of true (or equivalent), specifies that column balancing shall not occur, and each column shall be filled individually until the end of the current page, until all text has been displayed, even if this means one or more columns are unused.

[Example: Consider a WordprocessingML document with an initial section with three columns, defined by the following section properties:

  <w:cols w:num="3" w:space="720" />

The default presentation would have the text in that section balanced between those three columns:

However, if this compatibility setting is turned on:

  <w:noColumnBalance />

Then the columns are not balanced, and the contents of the section are used to fill each column to the bottom of the current page in succession, resulting in the following output:

The next section is now forced to begin on the next page, as the columns on page one extend to the bottom of that page. end example]

Parent Elements

compat (Part 1, §

This element’s content model is defined by the common boolean property definition in Part 1, §17.17.4.

© ISO/IEC29500: 2008.

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.