* IMHO there is a bug in itemgrops
@ 2014-11-13 13:41 Vasiliy Chirkov
2014-11-16 19:24 ` Hans Hagen
0 siblings, 1 reply; 2+ messages in thread
From: Vasiliy Chirkov @ 2014-11-13 13:41 UTC (permalink / raw)
To: ntg-context
Minimal example:
\starttext
\defineitemgroup[Enum][levels=3]
\setupitemgroup[Enum][each][fit][symbol=n]
\setupitemgroup[Enum][1][stopper={}]
\setupitemgroup[Enum][2][stopper={***}]
\setupitemgroup[Enum][3][stopper={******}]
\startEnum
\item item 1
\startEnum
\item item 1.1
\startEnum
\item item 1.1.1
\item item 1.1.2
\stopEnum
\item item 1.2
\stopEnum
\item item 2
\stopEnum
\stoptext
When option 'fit' is used with nested lists, calculated max item widths are saved in reverse order. Maxitemwidths are saved at first pass in \stopitemgrup in reverse order, while are read at second pass in \startitem grpoup in sequental order.
Am i right?
Best regards,
Vasiliy
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: IMHO there is a bug in itemgrops
2014-11-13 13:41 IMHO there is a bug in itemgrops Vasiliy Chirkov
@ 2014-11-16 19:24 ` Hans Hagen
0 siblings, 0 replies; 2+ messages in thread
From: Hans Hagen @ 2014-11-16 19:24 UTC (permalink / raw)
To: ntg-context
On 11/13/2014 2:41 PM, Vasiliy Chirkov wrote:
> Minimal example:
>
> \starttext
> \defineitemgroup[Enum][levels=3]
> \setupitemgroup[Enum][each][fit][symbol=n]
> \setupitemgroup[Enum][1][stopper={}]
> \setupitemgroup[Enum][2][stopper={***}]
> \setupitemgroup[Enum][3][stopper={******}]
>
> \startEnum
> \item item 1
> \startEnum
> \item item 1.1
> \startEnum
> \item item 1.1.1
> \item item 1.1.2
> \stopEnum
> \item item 1.2
> \stopEnum
> \item item 2
> \stopEnum
> \stoptext
>
> When option 'fit' is used with nested lists, calculated max item widths are saved in reverse order. Maxitemwidths are saved at first pass in \stopitemgrup in reverse order, while are read at second pass in \startitem grpoup in sequental order.
>
> Am i right?
yes, i'll fix it (i didn't assume nested fixed usage)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-11-16 19:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-11-13 13:41 IMHO there is a bug in itemgrops Vasiliy Chirkov
2014-11-16 19:24 ` Hans Hagen
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).