On Fri, 24 Jan 2003 16:33:22 +0100 Hans Hagen <[EMAIL PROTECTED]> wrote:
> 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)? It should be possible to use MetaFun and piechartMP together in a stand-alone MP file. In this case piechartMP writes depending on the TeX-mode (i.e. TeX,LaTeX,ConTeXT) a MP file <jobname>.pct that will be input again. The file looks like verbatimtex <TeX/LaTeX/ConTeXT preamble> etex pc_label[1]:=btex <some label text> etex ; pc_label[2]:=btex <another label text> etex ; ... verbatimtex <some code depending on the macro-package, i.e. \stoptext for ConTeXt> etex This seems to work only if it is employed not "inside" ConTeXt. (Why??) Therefore i have to use textext for the labels if piechartMP is used "inside" ConTeXt. In order to decide which way of label typesetting is needed i have to check some variable that shows me that piechartMP is used "inside" ConTeXt. But i cannot use one of the MetaFun variables, since MetaFun and piechartMP should also work together without ConTeXt. So, is there a variable set in the ConTeXt-MP-file that is _not_ provided by MetaFun? > >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. Does not work. Gives "Unable to make mpx file" message. Will investigate in this later, since the key-value interface troubles me much more. > >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) in the new release all internal variables are prefixed with "pc_" and all internal macros have the postfix "_pc". > [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] I know, but the colors of the outsides of the segments are calculated depending on the observation angle. Currently i don't understand how cmyk-colors are implemented, so i dont know how to deal with. transparencies will be available/used for drop-shadows if MetaFun is loaded. Jens _______________________________________________ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
