Re: [NTG-context] \startalign[n=3] don't work properly in MKIV
On Thu, 8 Sep 2011, Hongwen Qiu wrote: Hi, the following minimal example works fine in MKII, but the third columns are not aligned in MKIV \starttext \startformula\startalign[n=3] \NC X \NC = 1 + 2 \NC = 3 \NR \NC Y \NC = 1 + 2 + 3 \NC = 6 \NR \NC Z \NC = 1 + 2 + 3 + 4 \NC = 10 \NR \stopalign\stopformula \stoptext Is this a bug or the interface has changed in MKIV? This is a bug. I haven't investigated what is causing this. Aditya ___ 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 ___
[NTG-context] \startalign[n=3] don't work properly in MKIV
Hi, the following minimal example works fine in MKII, but the third columns are not aligned in MKIV \starttext \startformula\startalign[n=3] \NC X \NC = 1 + 2 \NC = 3 \NR \NC Y \NC = 1 + 2 + 3 \NC = 6 \NR \NC Z \NC = 1 + 2 + 3 + 4 \NC = 10 \NR \stopalign\stopformula \stoptext Is this a bug or the interface has changed in MKIV? $ context --version mtx-context | current version: 2011.09.06 17:46 $ luatex --version This is LuaTeX, Version beta-0.70.1-2011051918 (rev 4277) ___ 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 ___
Re: [NTG-context] repeat option in itemize not working correctly
On 8-9-2011 10:56, Wolfgang Schuster wrote:
It can be solved with something like this:
thanks for analyzing this
\def\doactualitemnumber
{\begingroup
>
%\c!numberconversionset=,
^^ we can use \c!numberconversionset=itemgroup:\currentitemgroup,
but my solution above doesn’t work with complex itemize constructs.
and then add (someplace) in the define macro:
\definestructureconversionset[itemgroup:#1][\currentitemconversionset][\currentitemsymbol]%
and at the end of the restarter:
\ifx\currentrepeatstart\empty
\let\currentitemconversionset\currentitemsymbol
\else
\edef\currentitemconversionset{\currentitemconversionset,\currentitemsymbol}%
\fi
which seems to work (baking a beta now)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-
___
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
___
Re: [NTG-context] Typesetting >> in verbatim
On 8-9-2011 10:39, Thomas Friedrich wrote: won't even compile. It doesn't like "<<". Question: Is there a way to replace the ">>" and"<<" strings in the typesetting environment by something else? Or another work around? this is because << >> is considered grouping just use mkiv Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
Re: [NTG-context] Typesetting >> in verbatim
Am Donnerstag, den 08.09.2011, 10:57 +0200 schrieb luigi scarso:
> On Thu, Sep 8, 2011 at 10:39 AM, Thomas Friedrich wrote:
>
> > Question: Is there a way to replace the ">>" and "<<" strings in
> > the typesetting environment by something else? Or another work around?
> >
> maybe
> \startHaskell
> foo = bar =/BTEX< foo = bar =/BTEX$<<$/ETEX print
> \stopHaskell
>
>
> --
> luigi
For anyone who's interested, I
will do the following now:
\startHaskell
foo /BTEX{\tt >>\!=}/ETEX bar
foo /BTEX>>\!=/ETEX bar
bar /BTEX{\tt =\!<<}/ETEX foo
bar /BTEX=\!
[NTG-context] refcard with context
Hi, I just came across an old layout of a reference card / cheatsheet of mine. See https://gist.github.com/1203210 and http://tex.stackexchange.com/questions/27832/template-for-cheatsheet/27853#27853 for an image how it looks like. Do with the code whatever you like (someone can perhaps put it as an example on the wiki?) Patrick ___ 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 ___
Re: [NTG-context] MKIV strange results in Adobe Reader
Am 08.09.2011 11:31, schrieb Hans Hagen:
> On 8-9-2011 11:19, Otso Helenius wrote:
>> Hello,
>>
>> I recently made a SimpleSlides presentation with MKIV (2011.08.27
>> 13:24). It looks ok on numerous PDF readers including Okular, Google
>> Docs, Sumatra PDF. Whenever I open it on Adobe Reader, the results are
>> rather puzzling:
>>
>> 1) The fifth page background is not black but grey, also some later
>> pages have grey background
>> 2) The RGB and CMYK swatch colours are all messed up
>>
>> The picture on page four has been intentionally corrupted with a hex
>> editor and then opened and saved again in Gimp to remove the errors in
>> the file.
>>
>> You can view the source here: https://pi-xi.net/share/colorlecture.tex
>> and the finished PDF here: https://pi-xi.net/share/colorlecture.pdf
>>
>> The only modifications I've made to the simpleslides-s-BottomSquares.tex
>> is replacing the background color, contrast color and variant color with
>> different values ([s=.0], [r=.8,g=.2,b=.2], [s=.15]).
>>
>> I would appreciate if someone could explain if there are bugs in my tex
>> sources, in MKIV or in the Adobe Reader – and in any case how can I fix
>> the erroneous output on Adobe Reader to match it on Sumatra, Google
>> Docs, etc.
>
> Do you use transparencies? On pages where they are used, a different
> color rendered seems to kick in (in acrobat).
>
You can try to add
\startluacode
function backends.codeinjections.rgbtransparencygroup()
local d = lpdf.dictionary {
S = lpdf.constant("Transparency"),
CS = lpdf.constant("DeviceRGB"),
I = true }
lpdf.registerpagefinalizer(function()
lpdf.addtopageattributes("Group",d) end)
end
\stopluacode
\def\pngTransparencyHack{\ctxlua{backends.codeinjections.rgbtransparencygroup()}}
\pngTranparencyHack
This is what I use here for my RGB based graphics. Anyhow, as the name
of the macro says: it's not more than a (RGB only) hack.
Regards, Peter
___
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
___
Re: [NTG-context] MKIV strange results in Adobe Reader
On 8-9-2011 11:19, Otso Helenius wrote: Hello, I recently made a SimpleSlides presentation with MKIV (2011.08.27 13:24). It looks ok on numerous PDF readers including Okular, Google Docs, Sumatra PDF. Whenever I open it on Adobe Reader, the results are rather puzzling: 1) The fifth page background is not black but grey, also some later pages have grey background 2) The RGB and CMYK swatch colours are all messed up The picture on page four has been intentionally corrupted with a hex editor and then opened and saved again in Gimp to remove the errors in the file. You can view the source here: https://pi-xi.net/share/colorlecture.tex and the finished PDF here: https://pi-xi.net/share/colorlecture.pdf The only modifications I've made to the simpleslides-s-BottomSquares.tex is replacing the background color, contrast color and variant color with different values ([s=.0], [r=.8,g=.2,b=.2], [s=.15]). I would appreciate if someone could explain if there are bugs in my tex sources, in MKIV or in the Adobe Reader – and in any case how can I fix the erroneous output on Adobe Reader to match it on Sumatra, Google Docs, etc. Do you use transparencies? On pages where they are used, a different color rendered seems to kick in (in acrobat). Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
[NTG-context] MKIV strange results in Adobe Reader
Hello, I recently made a SimpleSlides presentation with MKIV (2011.08.27 13:24). It looks ok on numerous PDF readers including Okular, Google Docs, Sumatra PDF. Whenever I open it on Adobe Reader, the results are rather puzzling: 1) The fifth page background is not black but grey, also some later pages have grey background 2) The RGB and CMYK swatch colours are all messed up The picture on page four has been intentionally corrupted with a hex editor and then opened and saved again in Gimp to remove the errors in the file. You can view the source here: https://pi-xi.net/share/colorlecture.tex and the finished PDF here: https://pi-xi.net/share/colorlecture.pdf The only modifications I've made to the simpleslides-s-BottomSquares.tex is replacing the background color, contrast color and variant color with different values ([s=.0], [r=.8,g=.2,b=.2], [s=.15]). I would appreciate if someone could explain if there are bugs in my tex sources, in MKIV or in the Adobe Reader – and in any case how can I fix the erroneous output on Adobe Reader to match it on Sumatra, Google Docs, etc. Best regards, Otso Helenius ___ 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 ___
Re: [NTG-context] Typesetting >> in verbatim
On Thu, Sep 8, 2011 at 10:39 AM, Thomas Friedrich wrote: > Question: Is there a way to replace the ">>" and "<<" strings in > the typesetting environment by something else? Or another work around? > maybe \startHaskell foo = bar =/BTEX
Re: [NTG-context] repeat option in itemize not working correctly
Am 08.09.2011 um 10:05 schrieb Aditya Mahajan:
> In MkIV, \startitemize[n,repeat] gives a result that does not look right. The
> numbers of the first level of itemize are missing.
As you brought this up I’ll add another problem with repeated items (it shows
also your problem). When you can the number format for a subitem the parent
number is also changed:
\starttext
\startitemize[n,repeat]
\item Item 1. \startitemize[n] \item Item 1.1. \item Item 1.2.
\stopitemize
\item Item 2. \startitemize[n] \item Item 2.1. \item Item 2.2.
\stopitemize
\stopitemize
\blank[2*line]
\startitemize[n,repeat]
\item Item 1. \startitemize[a] \item Item 1.a. \item Item 1.b.
\stopitemize
\item Item 2. \startitemize[a] \item Item 2.a. \item Item 2.b.
\stopitemize
\stopitemize
\blank[2*line]
\startitemize[n,repeat]
\noitem \startitemize[a] \item Item 1.a. \item Item 1.b. \stopitemize
\noitem \startitemize[a] \item Item 2.a. \item Item 2.b. \stopitemize
\stopitemize
\stoptext
It can be solved with something like this:
\def\doactualitemnumber
{\begingroup
\setupstructurecounter
[\currentitemgroupcounter]
[%\c!prefix=\v!no,
\c!prefix=\getitemparameter\currentitemlevel\c!prefix,
\c!prefixstopper=\getitemparameter\currentitemlevel\c!prefixstopper,
\c!prefixseparatorset=\getitemparameter\currentitemlevel\c!prefixseparatorset,
\c!prefixconversion=\getitemparameter\currentitemlevel\c!prefixconversion,
\c!prefixconversionset=\getitemparameter\currentitemlevel\c!prefixseparatorset,
\c!prefixset=\getitemparameter\currentitemlevel\c!prefixset,
\c!prefixsegments=\getitemparameter\currentitemlevel\c!prefixsegments,
\c!prefixconnector=\getitemparameter\currentitemlevel\c!prefixconnector,
\c!criterium=\getitemparameter\currentitemlevel\c!criterium,
\c!numberorder=\ifconditional\reverselistitem\v!reverse\else\v!normal\fi,
\c!numberstopper=\expdoif{\getitemparameter\currentitemlevel\c!placestopper}\v!yes{\getitemparameter\currentitemlevel\c!stopper},
%\c!numberseparatorset=,
%\c!numberconversionset=,
\c!numberconversion=\currentitemsymbol,
\c!numbersegments=\ifx\currentrepeatstart\empty\else\currentrepeatstart:\fi\number\currentitemlevel]%
\ifconditional\reverselistitem
\convertedstructurecounter[\currentitemgroupcounter]%
[\number\currentitemlevel]%
+ \else\ifconditional\repeatlistitem
+ \dostepwiserecurse\currentrepeatstart\currentitemlevel\plusone
+{\addvalue{repeatlist}{\getvalue{\@@globalitemsymbol\recurselevel}}}%
+
\normalexpanded{\definestructureconversionset[\??op::\v!repeat][\repeatlist][n]}%
+
\convertedstructurecounter[\currentitemgroupcounter][\c!numberconversionset=\??op::\v!repeat,\c!numberconversion=]
\else
\convertedstructurecounter[\currentitemgroupcounter]%
[\number\currentitemlevel]%
\fi
\dohandleitemreference
\endgroup}
but my solution above doesn’t work with complex itemize constructs.
Wolfgang
___
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
___
Re: [NTG-context] Typesetting >> in verbatim
Am Donnerstag, den 08.09.2011, 09:59 +0200 schrieb Wolfgang Schuster:
> Am 08.09.2011 um 09:55 schrieb Aditya Mahajan:
>
> > On Wed, 7 Sep 2011, Thomas Friedrich wrote:
> >
> >> Hi,
> >>
> >> I am having problems typing ">>" when typesetting code within a
> >> \definetyping environment.
> >>
> >> I hope someone might be able to give me a hint. My code looks as
> >> follows:
> >>
> >> \definetyping
> >> [Haskell]
> >> [ option=commands,
> >>before={\startframedtext[width=\makeupwidth,
> >> frame=off,bottomframe=on,topframe=on,
> >> background=screen,backgroundscreen=.90]},
> >>after={\stopframedtext},
> >>bodyfont=9pt,
> >>margin=1.5em]
> >>
> >> \startHaskell
> >> main = foo >>= bar
> >> \stopHaskell
> >>
> >> Whenever ConTeXt comes across >> anywhere in the text, it just doesn't
> >> typeset anything. So in the above case, I get the output:
> >>
> >> main = foo = bar
> >
> > Confirmed. >> are eaten in MkII but everything works fine with MkIV. My
> > guess is because of automatic ligatures for >>. My usual trick for
> > disabling such ligatures in MkII is
> >
> >\usetypescript [modern] [texnansi]
> >\setupbodyfont [modern]
> >
> > but that does not work in this case. There were some discussions in the
> > past about disabling ligatures in typewriter font, but I don't remember the
> > exact solution.
>
> No, the culprit is “option=commands" which gobbles “>>”.
>
> Wolfgang
You are absolutely right, Wolfgang. When removing the "option=commands"
from the definition, the ">>" won't get eaten. (Thanks!) However, my
whole code consists of things such as
\startHaskell
main = f1 /BTEX$\circ$/ETEX f2 >>= hey
\stopHaskell
How comes that the ">>" are gobbled? Even worse, something like
\startHaskell
foo = bar =<< print
\stopHaskell
won't even compile. It doesn't like "<<".
Question: Is there a way to replace the ">>" and "<<" strings in
the typesetting environment by something else? Or another work around?
Thanks,
Thomas
>
> ___
> 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
> ___
___
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
___
[NTG-context] repeat option in itemize not working correctly
In MkIV, \startitemize[n,repeat] gives a result that does not look right. The numbers of the first level of itemize are missing. \starttext \startitemize[n,repeat] \item One \item Two \startitemize[n] \item Sub one \item Sub two \stopitemize \stopitemize \stoptext I am using 2011.08.21. Aditya ___ 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 ___
Re: [NTG-context] setting margin for second level of itemize
On Thu, 8 Sep 2011, Wolfgang Schuster wrote:
Am 07.09.2011 um 17:49 schrieb Aditya Mahajan:
Hi,
I want items to display as follows (| represents the text area edge)
| 1. First item
| 2. Second item
| 2.1 Sub item
| 2.2 Sub item
| 3. Third item
I could not find a way to control the margin of the second level. Setting
\setupitemize[1][margin=2em]
\setupitemize[2][margin=4em]
does not work.
\setupitemize[1][margin=2em,width=2em]
\setupitemize[1][margin=2em,width=2em] % margin 2 = margin 1 + width 1
Thanks.
I prefer using itemalign=flushright with [broad,fit], which looks really
ugly with an explicit width. For example
\setupitemize[1][margin=2em,width=2em, distance=0.5em,
itemalign=flushright]
\setupitemize[broad,fit]
\showframe
\starttext
\startitemize[n]
\item One
\item Two
\startitemize[n]
\item Sub one
\item Sub two
\stopitemize
\dorecurse{10}{\item Item \recurselevel}
\stopitemize
\stoptext
But I guess that in this case I'll just remove \setupitemize[broad,fit].
Aditya
___
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
___
Re: [NTG-context] Typesetting >> in verbatim
Am 08.09.2011 um 09:55 schrieb Aditya Mahajan:
> On Wed, 7 Sep 2011, Thomas Friedrich wrote:
>
>> Hi,
>>
>> I am having problems typing ">>" when typesetting code within a
>> \definetyping environment.
>>
>> I hope someone might be able to give me a hint. My code looks as
>> follows:
>>
>> \definetyping
>> [Haskell]
>> [ option=commands,
>>before={\startframedtext[width=\makeupwidth,
>> frame=off,bottomframe=on,topframe=on,
>> background=screen,backgroundscreen=.90]},
>>after={\stopframedtext},
>>bodyfont=9pt,
>>margin=1.5em]
>>
>> \startHaskell
>> main = foo >>= bar
>> \stopHaskell
>>
>> Whenever ConTeXt comes across >> anywhere in the text, it just doesn't
>> typeset anything. So in the above case, I get the output:
>>
>> main = foo = bar
>
> Confirmed. >> are eaten in MkII but everything works fine with MkIV. My guess
> is because of automatic ligatures for >>. My usual trick for disabling such
> ligatures in MkII is
>
>\usetypescript [modern] [texnansi]
>\setupbodyfont [modern]
>
> but that does not work in this case. There were some discussions in the past
> about disabling ligatures in typewriter font, but I don't remember the exact
> solution.
No, the culprit is “option=commands" which gobbles “>>”.
Wolfgang
___
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
___
Re: [NTG-context] Typesetting >> in verbatim
On Wed, 7 Sep 2011, Thomas Friedrich wrote:
Hi,
I am having problems typing ">>" when typesetting code within a
\definetyping environment.
I hope someone might be able to give me a hint. My code looks as
follows:
\definetyping
[Haskell]
[ option=commands,
before={\startframedtext[width=\makeupwidth,
frame=off,bottomframe=on,topframe=on,
background=screen,backgroundscreen=.90]},
after={\stopframedtext},
bodyfont=9pt,
margin=1.5em]
\startHaskell
main = foo >>= bar
\stopHaskell
Whenever ConTeXt comes across >> anywhere in the text, it just doesn't
typeset anything. So in the above case, I get the output:
main = foo = bar
Confirmed. >> are eaten in MkII but everything works fine with MkIV. My
guess is because of automatic ligatures for >>. My usual trick for
disabling such ligatures in MkII is
\usetypescript [modern] [texnansi]
\setupbodyfont [modern]
but that does not work in this case. There were some discussions in the
past about disabling ligatures in typewriter font, but I don't remember
the exact solution.
Aditya
___
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
___
[NTG-context] Typesetting >> in verbatim
Hi,
I am having problems typing ">>" when typesetting code within a
\definetyping environment.
I hope someone might be able to give me a hint. My code looks as
follows:
\definetyping
[Haskell]
[ option=commands,
before={\startframedtext[width=\makeupwidth,
frame=off,bottomframe=on,topframe=on,
background=screen,backgroundscreen=.90]},
after={\stopframedtext},
bodyfont=9pt,
margin=1.5em]
\startHaskell
main = foo >>= bar
\stopHaskell
Whenever ConTeXt comes across >> anywhere in the text, it just doesn't
typeset anything. So in the above case, I get the output:
main = foo = bar
Thanks for you help!
Thomas
___
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
___
Re: [NTG-context] animation error
On 8-9-2011 06:57, Jeong Dalyoung wrote: Dear Woldgang, I replaced a line in scrn-fld.mkvi as you suggested. After compiling, animation worked well. Will it be fixed in the next beta? sure Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
