On 12/20/2017 6:44 PM, Aditya Mahajan wrote:
On Wed, 20 Dec 2017, Hans Hagen wrote:
% solution 1:
\setuphead
[part]
[page=no,
placehead=hidden]
\setuptexttexts
[\synchronizehead{part}]
I recently had a problem where \testpage was misbehaving while
\testpagesyncronized worked correctly. The example above is another
situation where syncronization solves the problem.
that is actually more tricky as trying toi sync the page buildern (and
spacing) is rather sensitive
Does syncronization have any drawbacks (other than speed)? If not, then
what is the overhead of "synchronizing everything"? ConTeXt is quite
fast, and I for one, wouldn't mind a few mili second delay in each
compilation for saving a few hours of debugging time!
normally i can deal with the speed (in this case it's probably not
measurable) and normally i manage to add features without much of a
penalty (of course sometimes it can mean hours of programming and
testing) ... speaking of speed, probably no one notices when context
becomes faster (mkiv definitely has not become slower over the years)
unless the fact that no one complains is a good sign
concerning syncing each time ... i can think of it but it needs an extra
set of state variables per head then (and probbaly a way to turn that
trickery off)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
