You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
2.11 mfpreadlog, \mfpreadlog. 8<br />
2.11 mfpreadlog, \mfpreadlog.<br />
From version 0.8, there exists a scheme to allow METAFONT or METAPOST to pass information<br />
back to the .tex file. This is done by writing code to the figure file requesting METAFONT to<br />
place that information in the .log file it produces. This option instructs MFPIC to read through<br />
that log file line-by-line looking for such information. Since such log files can be potentially quite<br />
lengthy, this is made an option. If the command form \mfpreadlog is used, it must come before<br />
the \opengraphsfile command, since that is when the file will be examined. At the present time,<br />
the only MFPIC facility that requires this two-way communication is \assignmfvalue (see subsection<br />
4.12.8). If this is used, the filename given to \opengraphsfile should not be the same as the<br />
TEX source file in which this occurs, as then the wrong .log may be read.<br />
2.12 Scoping Rules.<br />
Some of these options merely change TEX behavior, others write information to the output file for<br />
METAFONT or METAPOST. Changes in TEX behavior obey the normal TEX grouping rules, the information<br />
written to the output file obeys METAFONT grouping rules. Since each <strong>mfpic</strong> environment is<br />
both a TEX group and (corresponds to) a METAFONT group, the following always holds: use of one<br />
of the command forms inside of an <strong>mfpic</strong> environment makes the change local to that environment.<br />
An effort has been made (as of version 0.7) to make this universal. That is, any of the commands<br />
listed above for turning options on and off will be global when issued outside an <strong>mfpic</strong> environment.<br />
The debug commands are exceptions; they obey all TEX scoping rules.<br />
We have also tried to make all other MFPIC commands for changing the various parameters<br />
follow this rule: local inside <strong>mfpic</strong> environment, global outside. If this is ever untrue, and I don’t<br />
<strong>doc</strong>ument that fact, please let me know.<br />
The following are special:<br />
\usemetapost, \usemetafont, \<strong>mfpic</strong>draft, \<strong>mfpic</strong>final, \<strong>mfpic</strong>nowrite,<br />
and \mfpreadlog.<br />
Their effects are always global, partly because they should occur prior to the initialization command<br />
\opengraphsfile (described in section 4.1). Note that \usemetapost may cause a file of graphic<br />
inclusion macros to be input. If this command is issued inside a group, some definitions in that file<br />
may be lost, breaking the graphic inclusion code.