<div class="gmail_quote">On Wed, Sep 29, 2010 at 12:48 PM, David Doria <span dir="ltr"><<a href="mailto:daviddoria@gmail.com">daviddoria@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div class="im">On Wed, Sep 29, 2010 at 9:48 AM, Eric E. Monson <span dir="ltr"><<a href="mailto:emonson@cs.duke.edu" target="_blank">emonson@cs.duke.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">That's definitely a bug. It's like the data is getting painted on the first go-around based on the wrong axis range (wrong transform...?), but as soon as you resize the window it's recalculating something based on the new bounds and then it gets figured out properly. I don't have time to look into it right now, but hopefully Marcus will (be able to reproduce the problem and) recognize what's wrong.<div>
<br></div><font color="#888888"><div>-Eric</div></font><div><div><div><br></div></div></div></div></blockquote><div><br></div></div><div>Ah, yep, you're right, when I resize the window it appears correctly. Thanks for confirming this.</div>
<div></div></div></blockquote><div><br></div><div>Sigh...I have a one line patch (moving a call) that should fix this up. Thanks for pointing it out, it is an artifact introduced in the new font metric based layout code I added, but none of the other tests seemed to show the issue.</div>
<div><br></div><div>Marcus</div></div>