From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: buttons below visible area
Date: Wed, 04 Oct 2000 11:04:50 +0200 [thread overview]
Message-ID: <3.0.6.32.20001004110450.01519c90@pop.wxs.nl> (raw)
In-Reply-To: <20001003224514.09428@spi.power.uni-essen.de>
At 10:45 PM 10/3/00 +0200, Johannes Hüsing wrote:
>Another problem I am experiencing:
>
>When compiling the following source text, the defined menu which should be
>at the bottom of the page is off the page. If I set the height to value
>3\bottomheight, the buttons are cut off at the bottom, but at last readable.
>
>Any idea what I am doing wrong?
Sure, you define another level of menus,
\setupinteractionmenu[bottom][distance=overlay]
This command makes sure that the next level is layed over the previous one
(being bottom)
Also, I suggest that you use:
\startinteractionmenu[nav]
\but [PreviousJump] prev jump \\
\but [NextJump] next jump \\
\stopinteractionmenu
since it is more powerful,
Btw, I would do:
\setupinteractionmenu
[bottom]
[background=screen,
frame=on,
height=\bottomheight,
align=left,
distance=overlay,
style=small]
\defineinteractionmenu
[nav][bottom]
[state=start]
\startinteractionmenu[nav]
\but [PreviousJump] prev jump \\
\but [NextJump] next jump \\
\stopinteractionmenu
Now, if you're in for an experiment, try:
\setuppapersize[S6][S6]
\setupinteraction[state=start,menu=on]
\setupcolors[state=start]
\setuplayout
[topspace=12pt,header=0pt,height=100pt,footer=0pt,
bottomdistance=4pt,bottom=18pt,
backspace=12pt,margin=0pt,width=fit,edgedistance=12pt,rightedge=96pt]
\setupinteractionmenu
[bottom]
[background=screen,frame=on,height=\bottomheight,
style=small,align=left,distance=6pt]
\dorecurse
{10}
{\ExpandFirstAfter\defineinteractionmenu[\recurselevel][bottom][state=start]
\ExpandFirstAfter\startinteractionmenu[\recurselevel]
\but [PreviousJump] prev jump \\
\hfill Keep On Jumping \hfill
\but [NextJump] next jump \\
\stopinteractionmenu}
\starttext
\chapter[intro]{Introduction} \section[intro.purpose]{Purpose}
Just to type out some text which is unimportant. The bottom
of the screen counts.
\stoptext
And you will see why the distance is important. Try this with
distance=overlay and you'll find that you can define many many menu's, turn
them on and off on pages, let them overlay, etc etc. So, what you saw as a
problem, is actually a feature -)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
prev parent reply other threads:[~2000-10-04 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-03 20:45 Johannes Hüsing
2000-10-04 9:04 ` Hans Hagen [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=3.0.6.32.20001004110450.01519c90@pop.wxs.nl \
--to=pragma@wxs.nl \
--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).