From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Felix Ingram <f.ingram.lists@gmail.com>
Subject: Re: Tikz and \color
Date: Mon, 19 Sep 2011 13:41:52 +0200 [thread overview]
Message-ID: <4E772A80.2090000@wxs.nl> (raw)
In-Reply-To: <CAK5aKC_rUSAFO2bGJ3A=HLRjnuhDx4SesXB+aMdR_s4JKuGy_w@mail.gmail.com>
On 19-9-2011 13:10, Felix Ingram wrote:
> Hello all,
>
> I'm using Tikz to draw some fancy text boxes, but I've bumped into an
> annoying problem. If you run the example below then the body text will
> be rendered in red. If you remove the "REMOVE ME" text, then it will
> be rendered in black. I would expect the black version to be the
> correct version but I need to add text to my node.
> Am I using \color correctly? Does anyone know how I might go about
> debugging this? Is there a way to determine whether it's Context or
> Tikz that's misbehaving?
Tikz implements it own color handling and that interferes with the
handling built in context. The following works.
\usemodule[tikz]
\setuphead[section][after={\blackrule[color=red,width=125mm,height=1pt,depth=1pt]\vskip
2em}]
\starttext
\section{Some Title}
\dontleavehmode\forcecolorhack
\starttikzpicture
\node{x};
\stoptikzpicture
Flank sint culpa, dolore dolore ham hock chicken t-bone irure
pastrami. Eiusmod corned beef sint enim. Corned beef nulla qui aute,
meatloaf ground round cillum ex. Ut swine pork belly, tongue pig sed
tail frankfurter biltong ut bresaola anim. Jowl consequat tenderloin,
meatloaf fatback eu sint duis mollit chuck biltong. Nostrud cupidatat
nulla meatball, brisket irure dolor. Aliqua chuck ut in, nisi ea
t-bone shankle bresaola.
\stoptext
We can consider adding some dummy to the tikz wrapper (\char0 will do)
so that the context color mechanism gets reset before tikz doe some
literal juggling.
Anyway, when text precedes the picture it will go okay.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2011-09-19 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 11:10 Felix Ingram
2011-09-19 11:41 ` Hans Hagen [this message]
2011-09-19 12:28 ` Felix Ingram
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=4E772A80.2090000@wxs.nl \
--to=pragma@wxs.nl \
--cc=f.ingram.lists@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).