From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \defineframedtext take precedence over \defineframed and add "extra padding"
Date: Mon, 13 Jan 2014 20:39:25 +0100 [thread overview]
Message-ID: <D66F86E8-D32A-4A91-A728-133658744E14@gmail.com> (raw)
In-Reply-To: <CAGMMSTDnXohnjXsMYZg3p4x5xuMxdGAo3s7LdatX+F0yk=9g2A@mail.gmail.com>
Am 13.01.2014 um 19:55 schrieb Elspeth McGullicuddy <elspethmcgullicuddy@gmail.com>:
> In the following example \defineframedtext take precedence over
> \defineframed, and also I don't know how I can get rid of the "extra
> padding" (looks like a good \baselineskip before the text).
> (What I want is the first output, but with the readability of \startXY \stopXY)
>
> As for the "take precedence", I can change the name; But for the extra
> padding I don't know how to remove it.
> I could add a \vskip-\baselineskip at the beginning, but there is
> probably a better solution.
\usemodule[annotation]
\defineannotation
[blueframed]
[alternative=command,
command=\BlueFramedCommand]
\define[2]\BlueFramedCommand
{\BlueFramed{#2}}
\defineframed
[BlueFramed]
[width=local,
frame=off,
rulethickness=2mm,
backgroundoffset=1mm,
align=yes,
background=color,
backgroundcolor=lightblue,
corner=round,
radius=1.5mm]
\setupcolor[x11]
\starttext
\blueframed{\input{knuth}}
\startblueframed
\input{knuth}
\stopblueframed
\stoptext
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2014-01-13 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 18:55 Elspeth McGullicuddy
2014-01-13 19:39 ` Wolfgang Schuster [this message]
2014-01-13 20:12 ` Elspeth McGullicuddy
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=D66F86E8-D32A-4A91-A728-133658744E14@gmail.com \
--to=schuster.wolfgang@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).