From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: interaction colors and page break
Date: Fri, 7 Oct 2011 13:53:55 +0200 [thread overview]
Message-ID: <CAG5iGsAQFE8286E73q5NTr3aNq-HjR3DDh9dLa7w7LeXnFpc1A@mail.gmail.com> (raw)
In-Reply-To: <4E8DB65F.7040807@gmx.de>
On Thu, Oct 6, 2011 at 4:08 PM, Stefan Müller <warrence.stm@gmx.de> wrote:
> Hi,
>
> I think I found a small bug. The interaction colors interact strangely with
> page breaks in certain cases. See the following example. I'm using ConTeXt
> 201110003 12:59 MkIV.
>
> ################################
> \setupinteraction[state=start]
> \setupitemize[each][n, packed]
> \defineenumeration[myenum][text=Enumeration, location=top]
>
> \starttext
> \dorecurse{9}{\input ward \par}
>
> \startmyenum[enum]
> \startitemize
> \item Go to step \in[step].
> \item[step] Step.
> \stopitemize
> \stopmyenum
>
> Step \in[step] of \in{Enumeration}[enum]. These numbers shouldn't be red,
> should they? They are on the new page.
> \stoptext
> ################################
you can "help" ConTeXt with invisible vertical space \vskip0sp.
\setupinteraction[state=start]
\setupitemize[each][n, packed]
\defineenumeration[myenum][text=Enumeration, location=top,after=\vskip0sp]
\starttext
\dorecurse{9}{\input ward \par}
\startmyenum[enum]
\startitemize
\item Go to step \in[step].
\item[step] Step.
\stopitemize
\stopmyenum
Step \in[step] of \in{Enumeration}[enum]. These numbers shouldn't be
red, should they? They are on the new page.
--
luigi
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2011-10-07 11:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 14:08 Stefan Müller
2011-10-06 14:19 ` luigi scarso
2011-10-06 14:31 ` Stefan Müller
2011-10-06 14:44 ` luigi scarso
2011-10-06 14:49 ` Stefan Müller
2011-10-06 14:55 ` Stefan Müller
2011-10-06 15:42 ` Christian
2011-10-06 15:53 ` luigi scarso
2011-10-06 16:22 ` Christian
2011-10-07 11:53 ` luigi scarso [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAG5iGsAQFE8286E73q5NTr3aNq-HjR3DDh9dLa7w7LeXnFpc1A@mail.gmail.com \
--to=luigi.scarso@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).