Hallo,
Mojca Miklavec wrote:
You need \runMPgraphicstrue Yes, this helps!
But what are the sideeffects? When is the opposite needed?
\runMPgraphicfalse is faster when you need two tex runs anyway, because it collects all the graphics in a single metapost run which is a more efficient way of generating the graphics (in mkii), that is its reason for existence. But sometimes it doesn't work, so having \runMPgraphicstrue in your cont-usr.tex is not a bad idea.
I did this, but 'cont-usr.tex' is never included (windows minimal). The file 'core-job.tex' should do this but it is itself not included. Is 'core-job.tex' not needed? 'cont-sys.tex' has a commented entry \runMPgraphicstrue uncommenting this works. There is also a variable \runMPTEXgraphicstrue. What is this for? Should this be uncommented, too? Will this be overwritten with the next update? Wolfgang
Wolfgang Werners-Lucchini wrote:
I did this, but 'cont-usr.tex' is never included (windows minimal).
cont-usr is read by texexec --make (at format generation time)
The file 'core-job.tex' should do this but it is itself not included.
but it does (at format generation time)
'cont-sys.tex' has a commented entry \runMPgraphicstrue uncommenting this works.
yes, that is fine also
There is also a variable \runMPTEXgraphicstrue. What is this for? Should this be uncommented, too?
I think so, yes. (iirc, this is for textext() in mkii)
Will this be overwritten with the next update?
No, cont-sys.tex is never distributed Best wishes, Taco
participants (2)
-
Taco Hoekwater -
Wolfgang Werners-Lucchini