ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
* wrong order of content-list items if using balanced columnsets
@ 2006-02-27 22:14 Vit Zyka
  2006-02-28  1:00 ` Hans Hagen
  0 siblings, 1 reply; 3+ messages in thread
From: Vit Zyka @ 2006-02-27 22:14 UTC (permalink / raw)


Hello Wizards,

the next example illustrates the problem with wrong order of 
content-list items if using balanced columnsets:

-----------------------------------------------------------------
\setuplayout[grid=yes,topspace=1cm,bottomspace=1cm,height=middle]
\showgrid

\definecolumnset[A][n=2,balance=yes]
\setupcolumnsetlines[A][1][1][21]
\setupcolumnsetlines[A][1][2][21]
\definecolumnset[B][n=2,balance=yes]

\starttext
\startcolumnset[A]
   \section{Knuth}
   \dorecurse{2}{\input knuth \endgraf}
\stopcolumnset
\placeongrid{\hairline}
\startcolumnset[B]
   \section{Zapf}
   \dorecurse{1}{\input zapf \endgraf}
   \blank
   Content:
   \placecontent[criterium=all]
\stopcolumnset

\stoptext
--------------------------------------------------------------------

Problem is that the second section (Zapf) is inserted to .tui before the 
first one (Knuth). My observation: on the page where one columnset (A) 
is closed by \setupcolumnsetlines and the second (B) continues, .tuo 
contains marks from B firstly. This makes book content unsable in this 
configuration.

Any solutions? I am thinking about: Proper order writting to .tuo or to 
sort items according to mark number - it is correct (not sure if it is 
implemented?).

Thanks
Vit

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2006-02-28 14:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-02-27 22:14 wrong order of content-list items if using balanced columnsets Vit Zyka
2006-02-28  1:00 ` Hans Hagen
2006-02-28 14:51   ` Vit Zyka

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).