Thanks for fixing that. I forgot to mention when I added baseline alignment -- I really have no idea how to get a good baseline out of the usetex machinery, or if that's even possible.
Now that you've fixed that bug, the baseline-misalignment problem should only affect those who explicitly turn on baseline alignment (using valignment = "baseline" on a text object). If we can't get a baseline from usetex, we may have to decide whether it's worth keeping baseline alignment in as a feature at all... Cheers, Mike Jouni K. Seppänen wrote: > Xavier Gnata <[EMAIL PROTECTED]> writes: > >> I do not know if we should post bug reports against matplotlib svn. > > Posting bug reports is likely to be helpful, but I suspect the > developers' list might be more appropriate for bugs in the svn version. > For bugs in released versions, I think John has told people to file a > bug in the Sourceforge tracker and also send a message to the mailing > list. > >> Anyway, imshow is now fully broken this way : > [...] >> --> 200 w, h, d = renderer.get_text_width_height_descent( >> ValueError: need more than 2 values to unpack > > It's not in imshow really, but in the usetex branch of > get_text_width_height_descent in the agg backend. I fixed the immediate > problem, though baseline alignment is unlikely to work with usetex as of > now. > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
