ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Felix Ingram <f.ingram.lists@gmail.com>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Titles break TikZ
Date: Wed, 8 Feb 2012 14:14:04 +0000	[thread overview]
Message-ID: <CAK5aKC-wZpGY46-A_tLYADFuJhiPZn_DPQ3=zmhiWpkSXWgBqA@mail.gmail.com> (raw)
In-Reply-To: <4F327DAB.6040106@wxs.nl>

On 8 February 2012 13:50, Hans Hagen <pragma@wxs.nl> wrote:
> On 8-2-2012 12:16, Felix Ingram wrote:
>>
>> On 8 February 2012 10:24, Hans Hagen<pragma@wxs.nl>  wrote:
>>>
>>> On 8-2-2012 10:51, Felix Ingram wrote:
>>>>
>>>>
>>>> On 7 February 2012 13:06, Philipp A.<flying-sheep@web.de>    wrote:
>>>>
>>>>> with some recent beta (sorry for vagueness), tikz stopped working after
>>>>> titles. (i use first-setup.sh to install: these are the betas, not
>>>>> something different, right?)
>>>
>>>
>>>
>>> what does 'stop working' mean? some message?
>>
>>
>> "Stop Working" means "no longer get positioned where they should be
>> but still get drawn".
>>
>> In my case all graphics are shifted to the right by
>> Some-Unknown-Distance. In Philipp's case the various graphics parts
>> jump about. (I've seen something similar when drawing multiple nodes).
>>
>> I've included my minimal example below again. I wouldn't say that
>> titles are causing the issue, it just seems to be that the first
>> picture will render okay and then all others from then on will be
>> misplaced. In the example that Philipp gave removing the \section line
>> will still demonstrate the issue.
>>
>> Please let me know if there's any more information that I can provide.
>
>
> Interesting is that it matters if one puts colons after words:
>
> one % :
>
> \pic
>
> two:
>
> \pic
>
> Anyhow, the problem is that tikz messes around with cq. assumes nullfont to
> be in a certain state which is asking for troubles.
>
> In font-set.mkvi there is some provision for this (which I don't like), but
> anyhow, one can uncomment the \dorecurse line
>
> \def\font_preloads_reset_nullfont
>  {\dorecurse\plusseven{\fontdimen\recurselevel\nullfont\zeropoint}% keep en
> eye on this as:
>   \ctxcommand{resetnullfont()}% in luatex 0.70 this will also do the
> previous
>   \globallet\font_preloads_reset_nullfont\relax}
>
> maybe tikz should push/pop nullfont dimens to be on the safe side as there
> is no rule against setting nullfont
>
> (btw, this problem has shown up before)

Thanks Hans,

This is working. (Now I just need to remove all of the fudge factors I
added to my template). I've posted a bug report on the PGF/Tikz
tracker, so I will add your suggested fix to that and hopefully it
will get addressed there.

Felix
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2012-02-08 14:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 13:06 Philipp A.
2012-02-08  9:51 ` Felix Ingram
2012-02-08 10:24   ` Hans Hagen
2012-02-08 11:16     ` Felix Ingram
2012-02-08 13:50       ` Hans Hagen
2012-02-08 14:14         ` Felix Ingram [this message]
2012-02-08 16:31           ` Philipp A.
2012-02-08 16:36             ` luigi scarso
2012-02-08 17:18               ` Philipp A.
2012-02-08 17:37                 ` Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAK5aKC-wZpGY46-A_tLYADFuJhiPZn_DPQ3=zmhiWpkSXWgBqA@mail.gmail.com' \
    --to=f.ingram.lists@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).