On 27/10/2010 19:18, Marius wrote:
Hello, I had the same problem, so I desided to define colors by hand.
\definecolor [lightgray] [h=D3D3D3]
\usemodule[tikz]
\unprotect \pgfutil@definecolor{black}{gray}{0} \pgfutil@definecolor{gray}{gray}{0.5} \pgfutil@definecolor{lightgray}{gray}{0.9} \pgfutil@definecolor{white}{gray}{1} \protect
Yes, this is what I've resorted to. But it would be nice to define things properly.
If you want to fix script, you need to change line:
local cv = colors.value(attributes) The table "colors" is expected to have a function named "value" that take the "attributes" parameter as its sole parameter itself. It then assigns the result to the local variable cv. After some research, adding "local colors = global.attributes.colors" below the line "local prtcatcodes = tex.prtcatcodes" works. There is a catch however, you can't use opacity on these colors. I suppose we have to generate all the transparency level by using spot colors or something like
On Wed, Oct 27, 2010 at 22:08, Michael Murphy
into
local cv = attributes.colors.values
Just guess, untested.
Nope, doesn't work. Using
local colors = colors or { }
gets me a little further, but then complains that 'value' is a nil value. I don't know enough Lua to fix this either. Strangely, it seems to work on some older MkIV versions of ConTeXt...
Michael. ___________________________________________________________________________________ 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 ___________________________________________________________________________________