From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Andres Conrado Montoya <andresconrado@gmail.com>
Subject: Re: Strange behavior in somewhat complex layout (again)
Date: Thu, 27 Jun 2019 20:17:59 +0200 [thread overview]
Message-ID: <41b1aaff-2add-78ce-16ae-b84572579afb@gmail.com> (raw)
In-Reply-To: <CAGhDZhA0owFrJkzD7YTgACZ-qQOvMXWrM0FrusjqFYBKGk16jQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1814 bytes --]
Andres Conrado Montoya schrieb am 27.06.2019 um 19:22:
> Hi List, it seems my message went unnoticed, if you can help me out,
> please do. I'm an struggling with this layout.
>
> I'm trying to make something using bits and examples found here and
> elsewhere, but I'm hitting a wall. I know there's a flawed logic in my
> approach, but I can't figure it out. Any help is appreciated.
>
> Expected behavior of the following MWE:
> When starting a new chapter, check if the page is even (left page), if
> so, fill it with color, and start the chapter in the next odd page
> (right page), removing the header but leaving the footer in that
> start-chapter page; and if this is a start-chapter page, use a
> specific graphic overlay for the page, but if if not (if its a regular
> page), use another graphic.
>
> Result:
> The header still appears in the start-chapter page, if it comes after
> the color filled page. But, if the start-chapter page comes after a
> regular (even) page, everything works as expected (no color-filled
> page, no header in the start-chapter page).
>
> MWE:
>
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% START MWE
>
> [...]
>
> \startsetups [chapter:before]
> \doifoddpageelse
> {}
> {\pushbackground[page]
> \setupbackgrounds[page][background=color,backgroundcolor=rojo]
> \page[yes,right]
> \popbackground}
> \stopsetups
\startsetups [chapter:before]
\page
\doifoddpageelse
{}
{\pushbackground[page]
\setupbackgrounds[page][background=color,backgroundcolor=rojo]
\page[yes,header,footer,right]
\popbackground}
\stopsetups
> \setuphead[chapter]
> [width=20em,
> before=\directsetup{chapter:before},
Apply the above setup with
beforesection=\directsetup{chapter:before},
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 2752 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-06-27 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 4:44 Strange behavior in somewhat complex layout Andres Conrado Montoya
2019-06-27 17:22 ` Strange behavior in somewhat complex layout (again) Andres Conrado Montoya
2019-06-27 18:17 ` Wolfgang Schuster [this message]
2019-06-27 18:53 ` Andres Conrado Montoya
2019-06-27 19:17 ` 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=41b1aaff-2add-78ce-16ae-b84572579afb@gmail.com \
--to=wolfgang.schuster.lists@gmail.com \
--cc=andresconrado@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).