From: Sergey Slyusarev <cph.lmy@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Bug: \textext inside \*MPinclusions causes error
Date: Mon, 16 Jan 2017 22:31:39 +0300 [thread overview]
Message-ID: <CAHUe7fBG0_gEwNpczJc1qgSB8y3ZX1i5czVKn1kscKJ38XVSrg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1868 bytes --]
> the (subtle) difference between the two [*MPinclusions and **MPinitializations*] is not a bug but a feature
If I understood correctly, *MPinitializations affects everything and
can't be assigned to a specific instance (or can it?),
in some cases (like mine) this difference is not so subtle.
Look at the following example (not so minimal):
\startMPinitializations
picture p;
p := image(
draw fullsquare scaled 1cm;
draw textext("1");
);
\stopMPinitializations
\startMPinitializations
picture s;
s := image(
draw (fullsquare rotated 45) scaled 1cm;
draw textext("2");
);
\stopMPinitializations
\defineMPinstance[foo][initializations=yes]
\startMPcode{foo}
picture q;
q := image(
draw fullcircle scaled 1cm;
draw textext("3");
);
draw q;
\stopMPcode
\startMPcode{foo}
draw p;
draw q shifted (2cm, 0);
draw s shifted (4cm, 0);
\stopMPcode
\defineMPinstance[bar][initializations=yes]
\startMPcode{bar}
picture r;
r := image(
draw fullcircle scaled 1cm;
draw textext("4");
);
draw r;
\stopMPcode
\startMPcode{bar}
draw p;
draw r shifted (2cm, 0);
draw s shifted (4cm, 0);
\stopMPcode
First, it shows why *MPinitializations can't replace *MPinclusions for me
(it affects all instances),
and second, it silently produces produces some really unexpected results:
It looks like it should produce (by line)
A circle with "3" inside (yes)
A square with "1" inside (yes); A circle with "3" inside again (no, instead
it produces circle with "2" inside); A rhombus with "2" inside (no, instead
it produces a rhombus with "1")
and so on.
(tested on http://live.contextgarden.net/)
In fact, I failed to declare picture variable inside with text inside one
*MPcode environment and pass it to another safely
(text either disappears or changes to other text, and this time ConTeXt
returns no error), that surely is a bug?
Sergey
[-- Attachment #1.2: Type: text/html, Size: 4417 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 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 reply other threads:[~2017-01-16 19:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 19:31 Sergey Slyusarev [this message]
2017-01-17 8:35 ` Hans Hagen
2017-01-21 21:13 ` Sergey Slyusarev
2017-01-22 12:23 ` Hans Hagen
2017-02-13 22:36 ` Sergey Slyusarev
2017-02-14 12:13 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2017-01-12 11:23 Sergey Slyusarev
2017-01-15 17:55 ` Hans Hagen
2017-01-11 22:08 Sergey Slyusarev
2017-01-12 9:06 ` Hans Hagen
2017-01-12 16:53 ` Alan Braslau
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=CAHUe7fBG0_gEwNpczJc1qgSB8y3ZX1i5czVKn1kscKJ38XVSrg@mail.gmail.com \
--to=cph.lmy@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).