ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Grey background for pages belonging to last section of every chapter
Date: Fri, 30 Jan 2015 18:27:45 +0100	[thread overview]
Message-ID: <28763E80-A4F8-4CB6-8385-5A5FDED2E09B@gmail.com> (raw)
In-Reply-To: <ff90ce78efb46ffa1a994404b8fde17e.squirrel@webmail.xs4all.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1438 bytes --]


> Am 30.01.2015 um 18:17 schrieb Rob Heusdens <robheus@xs4all.nl>:
> 
> Problem is however resetting the background. In the after option of
> \setuphead will not work, the \page is ejected directly after the section
> title. I want to reset to normal background after the section itself
> finishes. After this special section (summary) always a new chapter begins
> (except perhaps the last summary).
> 
> Should I add that manually as the last command of every summary (where
> also the chapter ends), or is there some way to perform a command after
> the summary itself (at the location where one would place \stopsummary if
> using the \startsummary syntax) ends?
> 
> The background should only be displayed behind the text itself, not the
> whole text area (so if a section ends halfway of the page, the bottom part
> should have no background) with some extra space surrounding it
> (above,below,left,right) using the offset or perhaps backgroundoffset
> options of \setupframed).

Use text backgrounds.

\definetextbackground
  [SummaryBackground]
  [frame=off,
   background=color,
   backgroundcolor=gray]

\definehead[summary][section]

\setuphead
  [summary]
  [before=,
   beforesection={\blank\starttextbackground[SummaryBackground]},
   aftersection={\stoptextbackground\blank}]

\starttext

\startsection[title=Knuth]

\input{knuth}

\stopsection

\startsummary[title=Zapf]

\input{zapf}

\stopsummary

\stoptext

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 13303 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
___________________________________________________________________________________

  reply	other threads:[~2015-01-30 17:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30 15:13 Rob Heusdens
2015-01-30 16:18 ` Rob Heusdens
2015-01-30 16:34   ` Wolfgang Schuster
2015-01-30 17:17     ` Rob Heusdens
2015-01-30 17:27       ` Wolfgang Schuster [this message]
2015-01-30 18:28         ` Rob Heusdens
2015-01-30 19:05           ` Wolfgang Schuster
2015-01-30 20:36             ` Rob Heusdens
2015-01-30 20:43             ` Rob Heusdens
2015-02-02 11:51               ` Wolfgang Schuster
2015-02-02 13:00                 ` TOC with " Keith J. Schultz
2015-02-02 22:23                   ` Wolfgang Schuster

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=28763E80-A4F8-4CB6-8385-5A5FDED2E09B@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).