Difference between revisions of "Command/startMPinclusions"
< Command
Jump to navigation
Jump to search
({{MetaPost see also}}) |
m (/MetaPost) |
||
| Line 49: | Line 49: | ||
{{Forum|startMPinclusions}} | {{Forum|startMPinclusions}} | ||
| − | [[Category: | + | [[Category:Command/MetaPost|startMPinclusions]] |
Revision as of 11:41, 26 November 2012
\startMPinclusions
Syntax
| \startMPinclusions[...][...][...] | |
| [...] | text |
| [...] | text |
| [...] | text |
Description
Inside \startMPinclusions one can specify MetaFun code that you would like to be present in your MetaPost instance. It is generally used to define MetaPost functions, or to input files that contain them.
Example
\startMPinclusions input boxes ; vardef my_metapost_fun(expr var)= ... enddef ; \stopMPinclusions
See also
- \defineMPinstance
- \setupMPinstance
- \startMPinclusions
- \startMPenvironment — deprecated
- \startMPcode
- \startuseMPgraphic — dynamic graphics that are recompiled at every use
- \useMPgraphic — use a dynamic graphic
- \startuniqueMPgraphic — dynamic graphics that are recompiled when parameters (width, height, depth, background color, line color) change
- \uniqueMPgraphic — use a dynamic graphic
- \startreusableMPgraphic — static graphics that are compiled once
- \reuseMPgraphic — use a static graphic
- \startstaticMPfigure — standalone graphics
- \usestaticMPfigure — use a standalone graphic
- \startMPpage — a page just large enough to fit its MetaPost contents
- MetaFun - MetaPost in ConTeXt
Help from ConTeXt-Mailinglist/Forum
All issues with:
