From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mf <massifr@fastwebnet.it>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: offset for background overlay
Date: Mon, 13 Apr 2020 18:14:23 +0200 [thread overview]
Message-ID: <3a126c17-1e10-f116-5f90-166e6a3a979e@gmail.com> (raw)
In-Reply-To: <c2769e0d-143f-c3f5-12fe-9a6ceb8368ab@fastwebnet.it>
mf schrieb am 13.04.2020 um 17:21:
> Thanks also for the explanation of backgroundoffset: it's an offset
> relative only to the background, and it moves in the opposite direction
> of the content offset of \framed.
>
> Looks like \framed[...,offset=VALUE,backgroundoffset=frame,...] is
> equivalent to \framed[...,offset=VALUE,backgroundoffset=-VALUE,...].
>
> I tried to add something to the WIKI to show how it works, but the
> previews I got were not consistent with what I'm obtaining on my PC
> (with LMTX and "context --luatex"), so I gave up.
When you use "backgroundoffset=frame" you have to change the value for
"frameoffset" to get a result because "backgroundoffset" uses now the
"frameoffset" value.
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-04-13 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 14:15 mf
2020-04-11 17:41 ` Hans Hagen
2020-04-11 18:11 ` Wolfgang Schuster
2020-04-11 21:59 ` mf
2020-04-12 5:53 ` Wolfgang Schuster
2020-04-13 15:21 ` mf
2020-04-13 16:14 ` Wolfgang Schuster [this message]
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=3a126c17-1e10-f116-5f90-166e6a3a979e@gmail.com \
--to=wolfgang.schuster.lists@gmail.com \
--cc=massifr@fastwebnet.it \
--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).