ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Stefan Müller" <warrence.stm@gmx.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Labels in MetaPost (MetaObj)
Date: Sun, 23 Jan 2011 13:25:03 +0100	[thread overview]
Message-ID: <4D3C1E1F.80500@gmx.de> (raw)
In-Reply-To: <4D3C13B7.8040501@gmx.de>

On 23.01.2011 12:40, Stefan Müller wrote:
> On 22.01.2011 17:30, Aditya Mahajan wrote:
>> On Sat, 22 Jan 2011, Stefan Müller wrote:
>>
>>> So its either using text or using metaobj? Too bad, metaobj is quite
>>> fun... I still hope you guys can fix this, but it's not urgent (to me).
>>>
>>> Anyway, what does the [+] after \startMPinclusions? I did not find
>>> documentation for that on the wiki.
>>
>> \startMPinclusions
>> path a ;
>> \stopMPinclusions
>>
>> \startMPinclusions
>> a := (0,0) -- (1cm,0) ;
>> \stopMPinclusions
>>
>> will fail, because the second inclusions overwrites the first. If you
>> use [+], then the second inclusions in appended after the first.
>
> Thank you for the explanation. So if I only have one "inclusions
> section" it doesn't matter?
>
>>> Just as a wild guess I tested the example below today, trying to make
>>> use of the things Aditya said, but to no avail.
>>
>> The trick is to ensure that the offending code (assignObj) is not run
>> twice.
>
> Your example works perfect. Many thanks for that as well. I didn't
> realize, that assignObj is causing the trouble, but now it's obvious.
> I'm just curious: the MP-code is only run twice by context if it
> contains labels, right? Otherwise I don't understand why the assignObj
> isn't always failing.

Sorry for double posting... The method with "if not flag" is a bit 
arkward, because assignObj isn't the only problem. "rotateObj(s, 90)" 
would rotate the object 180 degrees instead of 90; when defining the 
relation between several objects some equations may became redundant (my 
script is rather complex and I'm not sure why some of the equations 
cause trouble).

Stefan
___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2011-01-23 12:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18 12:17 Stefan Müller
2011-01-20  8:59 ` Taco Hoekwater
2011-01-21 23:10   ` Hans Hagen
2011-01-22  1:38     ` Aditya Mahajan
2011-01-22 13:25       ` Stefan Müller
2011-01-22 16:30         ` Aditya Mahajan
2011-01-23 11:40           ` Stefan Müller
2011-01-23 12:25             ` Stefan Müller [this message]
2011-01-23 17:22               ` Aditya Mahajan
2011-01-23 21:14                 ` Stefan Müller
2011-01-24 15:34                   ` Stefan Müller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D3C1E1F.80500@gmx.de \
    --to=warrence.stm@gmx.de \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).