···
Hi,
just wondering. Is there a official way to signal ConTeXt from a module, that an extra run is needed?
Hi Peter, some time ago I got this answer from Hans: http://www.mail-archive.com/ntg-context@ntg.nl/msg45820.html (Today the table is “job.variables.tobesaved”.) Hth Philipp
I started thinking about adding bookkeeping for the created run time graphics. Graphic related changes can then be detected and, if necessary, extra runs can be started to update the changed graphics.
I need the second run to create and start the ImageMagick batch script, but the collected info in the *.tuc file prevents ConTeXt from starting a second/third run. Currently I use a batch file that simply deletes the *.tuc file and then calls 'context'. As there is no bookkeeping, all the graphics are recreated then.
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 ___________________________________________________________________________________
-- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments