From: <josephcanedo@gmail.com>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: Re: disappearing margin text
Date: Thu, 23 Jun 2016 19:42:30 +0000 [thread overview]
Message-ID: <5aa94ec56de74ddb996e6fb6f78eca7d@gmail.com> (raw)
In-Reply-To: <DAA8D52D-5583-468F-9626-64C4353A4B40@icloud.com>
[-- Attachment #1.1: Type: text/plain, Size: 2272 bytes --]
Hi, have you tried putting the \inmargin Inside before= in defineenumeration ? Seems to work fine (assuming you want the marginal note on same line as question.
Joseph
\defineblock[question]
\hideblocks[question]
\defineenumeration
[question]
[text=Question, before=\inmargin{margin}] %%%%%%
\setupblock[question][before=\startquestion,after=\stopquestion]
\setupinmargin[stack=continue]
\starttext
\beginquestion
Text
\endquestion
\beginquestion
Text
\endquestion
\useblocks[question]
\stoptext
Sent from Windows Mail
From: Jan Willem Flamma
Sent: Wednesday, June 22, 2016 3:17 PM
To: ntg-context@ntg.nl
Thanks for your reply Marco.
Indeed using different margin text I now see they are overlaid. Using your suggestion adds the margin text from Question 2 just underneath the margin text from Question 1.
I would like to position it next to Question 2 because I would like to use this feature to indicate question categories.
Regards,
Jan Willem
> On 22 jun. 2016, at 11:52, Jan Willem Flamma <jwfregister@icloud.com> wrote:
>
> Dear list members
>
> In the following MWE, the margin text appears at question 1 but not at question 2.
>
> How is this possible?
>
> Kind regards,
> Jan Willem
>
>
> MWE:
> \defineblock[question]
> \hideblocks[question]
>
> \defineenumeration
> [question]
> [text=Question]
>
> \setupblock[question][before=\startquestion,after=\stopquestion]
>
>
> \starttext
>
> \inmargin{margin}
> \beginquestion
> Text
> \endquestion
>
> \inmargin{margin}
> \beginquestion
> Text
> \endquestion
>
> \useblocks[question]
>
> \stoptext
___________________________________________________________________________________
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
___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 4752 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2016-06-23 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 9:52 Jan Willem Flamma
2016-06-22 10:20 ` Marco Patzer
2016-06-22 13:17 ` Jan Willem Flamma
2016-06-23 19:42 ` josephcanedo [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=5aa94ec56de74ddb996e6fb6f78eca7d@gmail.com \
--to=josephcanedo@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).