From: "Christian" <metan0r@gmx.de>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Metapost graphics in separate file, help needed
Date: Wed, 23 Nov 2011 19:23:19 +0100 [thread overview]
Message-ID: <008601ccaa0d$0068d9b0$013a8d10$@gmx.de> (raw)
Dear List,
I am experiencing a strange problem. I have a project, essentially with the following structure (desperate attempt to keep track of my stuff):
mainfile.mkiv:
% BOF
...lots of setups and settings...
\starttext
\input metapostgraphics.mkiv
\input chapter1.mkiv
\input chapter2.mkiv
\input chapter3.mkiv
\stoptext
% EOF
I generate the PDF with 'context mainfile.mkiv'
So far for the structure. Now my problem:
metapostgraphics.mkiv contains several (4) metapost graphics with \startuseMPgraphics{nameX} ... \stopuseMPgraphics.
In chapter2.mkiv I want to use them with \useMPgraphics{nameX}.
It worked well until today, when I added a fifth graphic. Then I suddenly get a frame with 'undefined' inside instead of the picture.
I tried everything, checked for typos, tried different names, double checked the MP-code etc. but to no avail.
It only works if I put the exact same MP-code between \startMPcode \stopMPcode directly in the chapter2.mkiv
What is wrong here? Am I missing something? Did I get the input mechanism all wrong?
___________________________________________________________________________________
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 reply other threads:[~2011-11-23 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 18:23 Christian [this message]
2011-11-23 19:07 ` Hans Hagen
2011-11-23 19:32 ` Aditya Mahajan
2011-11-23 19:50 ` Christian
2011-11-23 23:13 ` Hans Hagen
2011-11-23 19:58 ` Hans Hagen
2011-11-23 20:18 ` Christian
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='008601ccaa0d$0068d9b0$013a8d10$@gmx.de' \
--to=metan0r@gmx.de \
--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).