From: Marco <netuse@lavabit.com>
To: ntg-context@ntg.nl
Subject: Reference jump location
Date: Mon, 28 Mar 2011 12:51:54 +0200 [thread overview]
Message-ID: <20110328125154.001d32a7@glyph> (raw)
I have the feeling that this issue is well known, but I cannot find a solution
at the moment.
When clicking on a reference the jump goes underneath the heading making it
invisible. How to make the jump to a position that the heading stays visible?
Example:
\setupinteraction [state=start, focus=width]
\starttext
\completecontent [interaction=all]
\startchapter [title=Foo]
\stopchapter
\page
\startchapter [title=Bar]
\stopchapter
\stoptext
Marco
___________________________________________________________________________________
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
___________________________________________________________________________________
reply other threads:[~2011-03-28 10:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110328125154.001d32a7@glyph \
--to=netuse@lavabit.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).