ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Patrick Gundlach" <patrick@gundla.ch>
Subject: Re: howto overlayers on section head
Date: 11 Aug 2004 00:37:39 +0200	[thread overview]
Message-ID: <m2zn52wrf0.fsf@levana.de> (raw)
In-Reply-To: <4118B77E.5080604@bo.imm.cnr.it> (Eros Albertazzi's message of "Tue, 10 Aug 2004 13:54:38 +0200")

Hello,

[...]

> I have experimented with some other graphics but if I use "chapter"
> instead of "subject" as section heading the result is different.
> I believe it depends on your

Here is the important stuff:

> \def\HeadTitle#1#2{% ....
>          \framed[background=myhead]{#1#2}}

(which is the command without spacing)

> tighted to the latter heading and not to the former .
> Am I right?


you should use something like

\setuphead[chpater][command=\HeadTitle]

> Deeply down to low level TeX at this point?

This is partly high level ConTeXt (\framed, background) and low level
TeX (hfill,...).

> Is just a question to redefine a command adding
> background=something-of-mine ?

background has to be a color or an overlay or ...

> Then where these command are discribed?

They should be described in the main manual or the metafun manual.


Summary: define a metapost graphic, use \defineoverlay to access
the mp graphic and use \framed{} to access the overlay
(background=...) and use \setuphead (command=somecommand) to define
your own command that acesses the \framed[background=...].

Patrick
-- 
ConTeXt wiki: http://contextgarden.net
texshow-web:  http://texshow.contextgarden.net
List archive: http://archive.contextgarden.net

  reply	other threads:[~2004-08-10 22:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10  8:41 Eros Albertazzi
2004-08-10  9:43 ` Patrick Gundlach
2004-08-10 11:54   ` Eros Albertazzi
2004-08-10 22:37     ` Patrick Gundlach [this message]
2004-08-11  9:53       ` Eros Albertazzi
2004-08-11 10:36         ` Patrick Gundlach
2004-08-11 10:38         ` Patrick Gundlach

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=m2zn52wrf0.fsf@levana.de \
    --to=patrick@gundla.ch \
    --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).