On Thu, 12 Jan 2017 10:06:09 +0100 Hans Hagen <pra...@wxs.nl> wrote: > you can use > > \startMPinitializations > \stopMPinitializations > > as these are expanded each graphic run > > action pass 1 pass 2 > > definitions yes > extensions yes > inclus figure yes > initializations yes yes > metapost code yes yes > end figure yes yes
One needs to remember that MPlib goes through several runs, and many standard MP code examples are written for a single, mpost run. This means that code can fail if variables, for example, are not properly initialized (or re-initialized). Another example is reading from files in MP, as the file descriptors are kept open by default, reading on from where one stopped in a previous run. Alan ___________________________________________________________________________________ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________
