ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Ugly bug with TikZ in recent ConTeXt MKIV
Date: Thu, 18 Nov 2010 10:03:29 +0100	[thread overview]
Message-ID: <AANLkTikRfHhFMt-xZGGFTHnmqJgW3Hw1uTrNotQUAfdw@mail.gmail.com> (raw)
In-Reply-To: <4CE4E853.8020205@wxs.nl>

On Thu, Nov 18, 2010 at 09:48, Hans Hagen wrote:
> On 18-11-2010 12:00, Mojca Miklavec wrote:
>>
>> Dear Hans,
>>
>> The following example worked perfectly fine with the version of
>> ConTeXt MKIV I was using one hour ago (no idea which version, but
>> something less than two weeks old). It still works OK with MKII and it
>> works much worse in the real document that I'm using.
>>
>> In my document both images are completely screwed up. Here it's only
>> the second one and if I comment out the first one, the second figure
>> comes out fine, so I'm a bit clueless about what magic is going on
>> inbetween.
>>
>> Nothing in TikZ has changed (I'm still using the "frozen" version from
>> November 2009 from minimals), so it must have something to do with
>> ConTeXt MKIV. It just messes up with some boxes on the page in some
>> unpredictable way.

Hans,

thanks a lot for the really nice simple example.

> I have no clue ... maybe some magic tikz variable (or shared register) that
> does not get reset?

I have no clue either, but this has never been a problem before and it
still works perfectly in both pdfTeX and XeTeX. So something really
looks suspicious on the MKIV part.

I would love to help debugging, but I have zero clue what and where to look for.

> \usemodule[tikz]
>
> \starttext
>
> \startbuffer[1]
>    \starttikzpicture
>        \draw[->] (0,0)--(1cm,1cm);
>    \stoptikzpicture
> \stopbuffer
>
> % \ruledhbox{\getbuffer[1]}
>
> \ruledhbox
>  {\ruledhbox{\getbuffer[1]}
>   \ruledhbox{\getbuffer[1]}}
>
> \ruledhbox
>  {\ruledhbox{\getbuffer[1]}%
>   \ruledhbox{\getbuffer[1]}}
>
> \ruledhbox{\getbuffer[1]}
>
> \stoptext

Thanks,
    Mojca
___________________________________________________________________________________
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:[~2010-11-18  9:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 23:00 Mojca Miklavec
2010-11-18  8:25 ` Alan BRASLAU
2010-11-18  8:48 ` Hans Hagen
2010-11-18  9:03   ` Mojca Miklavec [this message]
2010-11-18  9:49     ` Hans Hagen
2010-11-18 16:56       ` Vedran Miletić
2010-11-18 17:32         ` Hans Hagen
2010-11-18 10:39     ` Hans Hagen
2010-11-18 13:06       ` Mojca Miklavec

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=AANLkTikRfHhFMt-xZGGFTHnmqJgW3Hw1uTrNotQUAfdw@mail.gmail.com \
    --to=mojca.miklavec.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).