At 04:04 PM 1/24/2003 +0100, you wrote:

The next release of piechartMP will provide ConTeXt support.
In text-mode 1 (SetupText) it will detect ConTeXt automatically,
and will use textext instead of current _makeText.
ok

Hans, can you give me a hint how i can test that piechartMP is
used "inside" ConTeXt? It is not enough to test for the MetaFun
macro/variables, since MetaFun can be used without ConTeXt too.
In what sense? You do check duplicate loading yourself, so where is the test needed for (or: what info do you need from context)?

BTW, i would recommend to use piechartMP stand-alone.
Currently i'm working on a new release that allows labels to be typeset using
ConText. You only have to call MetaPost like:
mpost --tex=texexec ...
or

  texexec --mptex somefile.mp

since it does some testing/cleanup on the mp file.

Since this release features a completely rewritten, key-value-based
user-interface it needs still some time to update the documentation.
ok, will you also use a namespace prefix (i saw a variable called K which will probably clash with user vars)

The work-around Hans gave in the previous mail will not work with
the new release anymore. So please don't change anything in ConTeXt.
-)

if you need a specific kind of support ...

[btw, i suppose that you're aware of the fact that you can use cmyk colors and transparencies, think of overlapping pies in transparent colors]

Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | [EMAIL PROTECTED]
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------

_______________________________________________
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context

Reply via email to