You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually listings will be paginated with colwidths set. In this case the colwidths will be the same for all pages, even when split_into_pages_by_var is breaking alisting up into a list prior to pagination.
In the corner case they are not, however, we can get listings that have different column widths for the different "pagination sections" it is split into. In extreme cases this can result in column pagination being entirely different between sections of the listing:
The Merc and Datsun sections are each separated into two pages, while the Dodge and AMC sections are separated into three, despite them being parts of the same listing.
Breaking the listing into parts after pagination begins (ie after paginate_listing is called) would not have this issue because the overall colwidths could be calculated before the split and thus apply to all parts. That is the intention of allowing packages to define do_forced_paginate, which does exactly this (see the page_by behavior for rtables).
The text was updated successfully, but these errors were encountered:
Usually listings will be paginated with colwidths set. In this case the colwidths will be the same for all pages, even when
split_into_pages_by_var
is breaking alisting up into a list prior to pagination.In the corner case they are not, however, we can get listings that have different column widths for the different "pagination sections" it is split into. In extreme cases this can result in column pagination being entirely different between sections of the listing:
gives us
The
Merc
andDatsun
sections are each separated into two pages, while theDodge
andAMC
sections are separated into three, despite them being parts of the same listing.Breaking the listing into parts after pagination begins (ie after
paginate_listing
is called) would not have this issue because the overall colwidths could be calculated before the split and thus apply to all parts. That is the intention of allowing packages to definedo_forced_paginate
, which does exactly this (see thepage_by
behavior for rtables).The text was updated successfully, but these errors were encountered: