Re: Runtime graphics

[Pierre VINET <vinp@globetrotter.net>]

Hi Hans,

Thank you for your reply. Here is the modified test.tex file following your
indications :

\starttext
\def\MPrunfile#1{\bufferprefix \MyMpRunFile.#1}
\def\MyMpRunFile{graphserieA}
\startMPrun
  input graphserieA
\stopMPrun
\externalfigure[\MyMpRunFile.1]
\externalfigure[\MyMpRunFile.2]
%
\def\MyMpRunFile{graphserieB}
\startMPrun
  input graphserieB
\stopMPrun
\externalfigure[\MyMpRunFile.1]
\externalfigure[\MyMpRunFile.2]
\stoptext
\end .

The test.pdf output now show four gray boxes with the following messages in
their center
"
    name: dummy
file: graphserieA.1
   state: unknown
"
(with graphserieA.2 in the 2nd box, graphserieB.1 in the 3rd, etc.)

The test.log file tell
"
\openout5 = `test-mprun.mp'.
system(mpost -progname=mpost -mem=metafun test-mprun)...executed.

figures        : figure graphserieA can not be found
figures        : figure graphserieA can not be found
\openout5 = `test-mprun.mp'.

system(mpost -progname=mpost -mem=metafun test-mprun)...executed.

figures        : figure graphserieB can not be found
figures        : figure graphserieB can not be found
"

The figures are not found because a file named "test-mprun.mp" is still
created and metapost's output are still named "test-mprun.*" instead of
"\MyMpRunFile.*". Obviously, \externalfigure can not found any
"\MyMpRunFile.*" files.

If I use \externalfigure[mprun.*] instead of
\externalfigure[\MyMpRunFile.*], then the first metapost's output files
"test-mprun.1" and "test-mprun.2" are still re-used -?by \externalfigure?-
after the second \startMPrun .. \stopMPrun call. (A -?simple?- way to avoid
this systematic re-use of metapost's output would be, in my opinion, the
best of all solutions).

In the present case, I think the problem could be resolved if the
"*-mprun.mp" files were labeled with the prefix name of the metapost file
instead of the "jobname". Thus, for instance, we may read in the log file
after the first \startMPrun .. \stopMPrun call

\openout5 = `graphserieA-mprun.mp'.
system(mpost -progname=mpost -mem=metafun graphserieA-mprun)...executed.

and after the second \startMPrun .. \stopMPrun call

\openout5 = `graphserieB-mprun.mp'.
system(mpost -progname=mpost -mem=metafun graphserieB-mprun)...executed.

Afterwards, metapost's output files named "graphserieA-mprun.1",
"graphserieA-mprun.2", "graphserieB-mprun.1" and "graphserieB-mprun.2" would
be created and then normally found by \externalfigure.

Thanks again,

-- pv

> 
> 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

>> 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.