From: Ed L Cashin <ecashin@coe.uga.edu>
Cc: ntg-context@ntg.nl
Subject: Re: I spoke too soon.
Date: 09 Aug 2000 12:16:48 -0400 [thread overview]
Message-ID: <m3u2cuh0jz.fsf@coe.uga.edu> (raw)
In-Reply-To: <3.0.6.32.20000809094124.008a4c10@pop.wxs.nl>
Hans Hagen <pragma@wxs.nl> writes:
> At 03:13 AM 8/9/00 -0400, you wrote:
...
> >I notice that with the beta context my menu is not showing up, even in
> >my old documents that have menus that have always worked before.
> >
> >I'm using \completecontent, though.
>
> \starttext
> \completecontent
> \chapter {first}
> \chapter {second}
> \stoptext
>
> This really should produce a toc. It does here and I run the same version
> as you do. BTW, the new version also has:
Oh, the TOC shows up fine. I was referring specifically to the menu
button at the bottom of the page that points back to the TOC.
...
> \startmenu[right]
> \placelist[chapter][criterium=all]
> \vfill
> \but [CloseDocument] stop reading now \\
> \stopmenu[right]
That is weird. "\startmenu" and "\stopmenu" are not defined for me,
and putting the bracketed "[right]" after \stopinteractionmenu means
that "[right]" gets printed in the document text itself.
...
> Concerning menu's are you sure you have set
>
> \setupinteraction[menu=on]
Yes, it's in a block like this:
\startnotmode [printing]
\setupinteractionscreen[option=max]
\setupinteraction [state=start,color=blue,menu=on]
\setuppagenumbering [location=]
\stopnotmode
... and I'm sure that's getting evaluated, since the document is
starting full-screen.
Anyway, this is not an emergency. :) So if you are busy, I can wait
until after TUG2000.
--
--Ed Cashin PGP public key:
ecashin@coe.uga.edu http://www.coe.uga.edu/~ecashin/pgp/
next prev parent reply other threads:[~2000-08-09 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-01 20:08 David Arnold
2000-08-02 6:51 ` Hans Hagen
2000-08-02 7:19 ` David Arnold
2000-08-09 7:13 ` Ed L Cashin
2000-08-09 7:41 ` Hans Hagen
2000-08-09 16:16 ` Ed L Cashin [this message]
2000-08-09 21:00 ` Hans Hagen
2000-08-02 7:43 ` David Arnold
2000-08-02 10:14 ` Hans Hagen
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=m3u2cuh0jz.fsf@coe.uga.edu \
--to=ecashin@coe.uga.edu \
--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).