In the default setting, a Doc object has one "Pages" object as root of pages.
All "Page" objects are created as a kid of the "Pages" object.
Since a "Pages" object can own only 8191 kids objects, the maximum number of pages are 8191 page.
Additionally, the state that there are a lot of "Page" object under
one"Pages" object is not good, because it causes performance degradation of a viewer application.
An application can change the setting of a pages tree by invoking setPagesConfiguration().
If pagePerPages parameter is set to more than zero, a two-tier pages tree is created.
A root "Pages" object can own 8191 "Pages" object, and each lower "Pages" object can own pagePerPages "Page" objects.
As a result, the maximum number of pages becomes 8191 * pagePerPages page.
An application cannot invoke setPageConfiguration() after a page is added to document
In the default setting, a Doc object has one "Pages" object as root of pages.
All "Page" objects are created as a kid of the "Pages" object. Since a "Pages" object can own only 8191 kids objects, the maximum number of pages are 8191 page. Additionally, the state that there are a lot of "Page" object under one"Pages" object is not good, because it causes performance degradation of a viewer application.
An application can change the setting of a pages tree by invoking setPagesConfiguration(). If pagePerPages parameter is set to more than zero, a two-tier pages tree is created. A root "Pages" object can own 8191 "Pages" object, and each lower "Pages" object can own pagePerPages "Page" objects. As a result, the maximum number of pages becomes 8191 * pagePerPages page. An application cannot invoke setPageConfiguration() after a page is added to document