On 2013–02–14 Keith J. Schultz wrote:
> with your example below I noticed that the red circle is not
> quite in the graphic. it seems to be clip on the right!
It's fine on my machine, or maybe I just don't see it.
Marco
signature.asc
Description: Digital signature
_
Hi Marco,
It is not much, but I do see it.
Maybe around a tenth of a millimeter is missing! just a guess.
Looking closer the top is, also clipped!
regards
Keith
Am 14.02.2013 um 09:23 schrieb Marco Patzer :
> On 2013–02–14 Keith J. Schultz wrote:
>
>> with your example below I notic
On 2013–02–14 Marco Patzer wrote:
> Now I can use “n” in all MP instances (unless switched off for the
> particular instance). I'd like to define some variables only visible
> in instance “foo”. Something like
>
> \startMPinitializations [foo]
> numeric n; n=4cm;
> \stopMPinitializations
Thanks, got the following now working:
\def\startxmlbuffer{\grabbufferdata[xmlbuffer][startxmlbuffer][stopxmlbuffer]}
\def\stopxmlbuffer{\endinput}
..
\xmlprocessbuffer{dvd}{xmlbuffer}{}
Hans van der Meer
On 13 feb. 2013, at 22:34, Wolfgang Schuster
wrote:
>
> Am 13.02.2013 um 17:49 schrie
Hi Marco,
i think that ou have to specify the path completely
\setupexternalfigures[directory={/Users/willi/Documents/BOEDE/Logos}]
Willi
On Feb 13, 2013, at 2:15 PM, Marco Patzer wrote:
> On 2013–02–08 Hans Hagen wrote:
>
>> default: texmftree
>> local : relative to source
>> global : path l
On 2013–02–14 Willi Egger wrote:
> i think that ou have to specify the path completely
>
> \setupexternalfigures[directory={/Users/willi/Documents/BOEDE/Logos}]
That does not work for me, does this work on you machine?
Even if it would work, mandating an absolute path is wrong in my
opinion. Th
When one has
\startbuffer
…
\stopbuffer
or
\startbuffer[abc]
…
\stopbuffer
Is it possible to find in a redefined \stopbuffer the identity of the buffer in
question?
For example to do \def\stopbuffer{\doif{BUFFERIDENTITY}{abc} …}
Hans van der Meer
_
I am glad to see that I am not alone being confused...
We have:
\defineMPinstance
[name]
[\s!format=metafun,
\s!extensions=\v!yes,
\s!initializations=\v!yes,
\c!method=\s!default,
\c!textstyle=,
\c!textcolor=]
also, \setupMPinstance
So that extensions=yes|no and initializatio
On 2013–02–14 Alan BRASLAU wrote:
> So that extensions=yes|no and initializations=yes|no controls the use
> of MPextensions and MPinitializations. It seems that extensions is
> intended for all instances ("when enabled").
>
> From what I can see, extensions are read "once", initializations "each"
On Thu, 14 Feb 2013 19:14:46 +0100
Marco Patzer wrote:
> > I still have not figured out how to specify MPinclusions for a
> > particular instance.
>
> Try \startMPdefinitions{myinstance}
This is *not* the same as MPinclusions!
We may have an instance with its own MPdefinitions, already,
to w
Am 14.02.2013 um 18:59 schrieb Alan BRASLAU :
> I still have not figured out how to specify MPinclusions for a
> particular instance.
That’s not supported, the settings are applied to all instances and you only
enable or disable them.
Wolfgang
__
Am 14.02.2013 um 18:26 schrieb "Meer, H. van der" :
> When one has
> \startbuffer
> …
> \stopbuffer
>
> or
> \startbuffer[abc]
> …
> \stopbuffer
>
> Is it possible to find in a redefined \stopbuffer the identity of the buffer
> in question?
> For example to do \def\stopbuffer{\doif{BUFFERIDENT
On 2/14/2013 7:14 PM, Marco Patzer wrote:
On 2013–02–14 Alan BRASLAU wrote:
So that extensions=yes|no and initializations=yes|no controls the use
of MPextensions and MPinitializations. It seems that extensions is
intended for all instances ("when enabled").
From what I can see, extensions are
13 matches
Mail list logo