From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Runtime graphics
Date: Sat, 14 Jun 2003 11:06:11 +0200 [thread overview]
Message-ID: <5.2.0.9.1.20030614110347.02d1d5a0@localhost> (raw)
In-Reply-To: <BB0EDAB9.4651%vinp@globetrotter.net>
At 01:34 13/06/2003 -0400, you wrote:
> Hi,
>
> I run this simple test file test.tex :
>
>%&cont-en
>\setupoutput[pdftex]
>\runMPgraphicstrue
>\starttext
>\startMPrun
> input graphserieA
>\stopMPrun
>\externalfigure[mprun.1]
>\externalfigure[mprun.2]
>%
>\startMPrun
> input graphserieB
>\stopMPrun
>\externalfigure[mprun.1]
>\externalfigure[mprun.2]
>\stoptext
>\end .
>
> In the logfile, I got the messages :
>
>figures : figureobject test-mprun.1 is reused
>figures : figureobject test-mprun.2 is reused
>
> and twice the figures of graphserieA.mp on test.pdf.
>
> Is there a way to avoid the re-use of test-mprun.1 and test-mprun.2, I mean
>a way to overwrite the files test-mprun.1 and test-mprun.2 ?
>
> Or a way to get different names for each metapost output as, for example,
>graphserieA-mprun.1, graphserieA-mprun.2 and graphserieB-mprun.1,
>graphserieB-mprun.2 ?
>
> I could also give a different number to each of the figures in all of the
>*.mp files, but this solution is not pacticable since I have plenty of
>metapost files to process, each of it containing a lot of figures already
>numbered with almost the same numbers. Moreover, those numbers can not be
>modified because the figures are elsewhere referenced by their number and by
>the name of the metapost file.
You can redefine:
\def\MPrunfile#1{\bufferprefix mprun.#1}
to for instance
\def\MPrunfile#1{\bufferprefix \MyMpRunFile.#1}
\def\MyMpRunFile{mprun}
and them change the definition of \MyMpRunFile whenever you want
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2003-06-14 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 5:34 Pierre VINET
2003-06-14 9:06 ` Hans Hagen [this message]
2003-06-15 6:45 ` Pierre VINET
2003-06-15 18:03 ` Hans Hagen
2003-06-16 5:09 ` Pierre VINET
2003-07-01 10:20 ` bib module/cite Martin Moncrieffe
2003-07-11 13:01 ` bib module/cite (Context bug) Taco Hoekwater
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=5.2.0.9.1.20030614110347.02d1d5a0@localhost \
--to=pragma@wxs.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).