From: "Meer, Hans van der" <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: useMPgraphic scaling
Date: Tue, 26 Apr 2016 06:50:11 +0000 [thread overview]
Message-ID: <90E0EEAB-EF63-4F30-8B9B-B56A5193A32B@uva.nl> (raw)
In-Reply-To: <8d96c4d0-475d-f7fb-e2ed-379fdd1db867@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 825 bytes --]
On 25 Apr 2016, at 16:34, Hans Hagen <pragma@wxs.nl<mailto:pragma@wxs.nl>> wrote:
On 4/25/2016 3:46 PM, Meer, Hans van der wrote:
Thanks,
Your reply popped up here exactly the moment I saw the light! Must be
something
Messed up the order things:
Was:
\scale[\scalesetting]{%
\expanded{\useMPgraphic{\xmlatt{#1}{name}}{\xmlatt{#1}{parameters}}}}%
And of course had to be:
\expanded{\scale[\scalesetting]{%
\useMPgraphic{\xmlatt{#1}{name}}{\xmlatt{#1}{parameters}}}}%
is the \expanded really needed?
Sure, is needed. Checked it again.
I define \scalesetting as
\edef\scalesetting{scale=\xmlattdef{#1}{scale}{1000}}
But I am not sure why this needs the expansion..
The enclosing \rotate[rotation=\xmlattdef{#1}{rotation}{0}]{...} does not need the \expanded.
Hans van der Meer
[-- Attachment #1.2: Type: text/html, Size: 3869 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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-04-26 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 11:11 Meer, Hans van der
2016-04-25 11:22 ` Hans Hagen
2016-04-25 13:46 ` Meer, Hans van der
2016-04-25 14:34 ` Hans Hagen
2016-04-26 6:50 ` Meer, Hans van der [this message]
2016-04-26 7:15 ` 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=90E0EEAB-EF63-4F30-8B9B-B56A5193A32B@uva.nl \
--to=h.vandermeer@uva.nl \
--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).