From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: macro beginner question
Date: Sat, 05 Jun 2010 15:04:14 +0200 [thread overview]
Message-ID: <4C0A4B4E.3080007@elvenkind.com> (raw)
In-Reply-To: <1666900C-78F6-4A86-88A9-E0E6B92B97E4@gmail.com>
Bernhard Rosensteiner wrote:
> deleting the \def\Mycolor line does not help - same result.
No, that would definitely not help. Your problem was not the
definition, but that you never actually called the macro.
You should put the definition back, and add \Mycolor to the
\OpticalTest macro, perhaps like so:
\def\OpticalTest[#1]#2{%
\addff{\OOFeature}%
\definedfont[#2 at \OOSize]%
\setupinterlinespace
\hbox to \textwidth{\clip[width=.39\textwidth,
bottomoffset=\strutdepth]{%
\Mycolor
..\hbox to .39\textwidth etc. etc.
> best regards
> Bernhard
>
>
>
> Am 05.06.2010 um 14:34 schrieb Taco Hoekwater:
>
>> Bernhard Rosensteiner wrote:
>>> Hello all,
>>> in the process of learning macro programming in context i encountered the following problem (minimal example is attached):
>>> When i have \setuphead[section][color={red}] the color key influences in a strange way my „novice macro“ (see the text which should be black but is red). Further more the \ruledhbox in my macro stops at some point the red color (with a normal \hbox all the text in the section is red). what i´m doing wrong here? I don’t expect such a behaviour
>> Somewhere you should execute \Mycolor, you are only defining it.
>>
>> Best wishes,
>> Taco
>> ___________________________________________________________________________________
>> 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
>> ___________________________________________________________________________________
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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:[~2010-06-05 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 12:06 Bernhard Rosensteiner
2010-06-05 12:34 ` Taco Hoekwater
2010-06-05 12:50 ` Bernhard Rosensteiner
2010-06-05 13:04 ` Taco Hoekwater [this message]
2010-06-05 13:35 ` Bernhard Rosensteiner
-- strict thread matches above, loose matches on Subject: below --
2010-06-05 12:03 Bernhard Rosensteiner
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=4C0A4B4E.3080007@elvenkind.com \
--to=taco@elvenkind.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).