From: "Michal Kvasnička" <prgosek@gmail.com>
To: ConTeXt <ntg-context@ntg.nl>
Subject: Interactive slides---hidden field on every page
Date: Mon, 17 Sep 2007 00:34:36 -0500 [thread overview]
Message-ID: <f677a8e00709162234l6bc5130dpd5975585312c4e42@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2035 bytes --]
Good morning or whatever you have now in Europe.
It seems that my mail have come to the list, so I dare to repost it:
I'm preparing my slides. Every slide is divided to three parts
(backgrounds): text, header, and bottom. I've got the navigation buttons in
the bottom. Now I'd like to add one more button that would open a field on
the current page---a field containing the list of content. I'd like it to go
to the \Topic I want to discuss and disappear.
I tried this:
\definefield[Content][check][HelpSetup][content][content]
\setupfields[reset]
\setupfield[HelpSetup]
[width=fit,height=fit,frame=off,option={readonly,hidden}] %
\definesymbol[content][\SomeContentText]
\def\SomeContentText{%
\startframedtext
[width=\textwidth, height=fit, frame=on,
background=color, backgroundcolor=tmava,framecolor=svetla]%
\placecontent}
\stopframedtext
}
%
\setupbackgrounds
[text]
[%backgroundoffset=10pt,%.5cm,
background={contentmenu,nextpage}]
%
\defineoverlay
[ContentOnOff]
[{\goto{\framed[width=\overlaywidth,height=\overlayheight,frame=off]{\hss}}%
[JS(Toggle_Hide{Content})]}]%\overlaybutton{JS(Toggle_Hide{Content})}]
%
\startinteractionmenu[bottom]
\setupinteraction
[color=svetla,
contrastcolor=black]
\hbox to 600pt{%
\raise0.4em\hbox{%
\framed[width=3em, height=0.7em, frame=off,
background={PageCounter,ContentOnOff}]{}}
\hss
\interactionbuttons[frame=off, width=8em]
[firstpage,
previouspage,nextpage,
lastpage,
PreviousJump,NextJump]%
\hbox to 1cm{\hss}%
\hbox to 44mm{%
\interactionbuttons[frame=off][CloseDocument]\hss}%
}
However, it doesn't work:
1. The list of content is placed only on one page, not at all of them as I
would like.
2. The field supposed to show/hide it isn't clickable---it isn't
interactive, and does nothing.
3. I use \Topic and \Subject as heads, and I don't know how to put them to
the list of content.
Can you possibly help me to solve this problem?
Sincerely yours
Michal Kvasnicka
[-- Attachment #1.2: Type: text/html, Size: 2718 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2007-09-17 5:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 5:34 Michal Kvasnička [this message]
2007-09-17 14:28 ` Peter Rolf
-- strict thread matches above, loose matches on Subject: below --
2007-09-12 13:25 Michal Kvasnička
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=f677a8e00709162234l6bc5130dpd5975585312c4e42@mail.gmail.com \
--to=prgosek@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).