Hi all,
I agree with JDH.
Unfortunately, work has been exceptionally hectic so I haven't begun
the patch (if you don't count the hack job I did to install it for
myself).
Hi Adam,
As noted above, I haven't started a patch yet but I would be up for
working with you on one. It sounds like we can
Hi Brian,
I wrote the code in PyGTK that uses PyOS_InputHook for interactivity, as well
as the Mac OS X native backend for matplotlib that uses PyOS_InputHook in
exactly the same way. PyQT and Tkinter also use PyOS_InputHook, though the code
is a bit kludgy on Windows. So I definitely agree tha
Dear all,
I asked in the user list for a way to have only left and bottom border
in figure frame
(http://sourceforge.net/mailarchive/forum.php?thread_name=1233927942.20817.1.camel%40mineat2.hmi.de&forum_name=matplotlib-users)
Tony S Yu has kindly give a solution and a implementation that maybe i
On Mon, Feb 9, 2009 at 17:08, Jayson Barr wrote:
> I agree with JDH.
Likewise.
> Unfortunately, work has been exceptionally hectic so I haven't begun
> the patch (if you don't count the hack job I did to install it for
> myself).
Same here, I'm really busy with work and don't have much time to
Michiel,
Thanks for jumping into the discussion.
> I wrote the code in PyGTK that uses PyOS_InputHook for interactivity, as well
> as the Mac OS X native backend for matplotlib that uses PyOS_InputHook in
> exactly the same way. PyQT and Tkinter also use PyOS_InputHook, though the
> code is a
The PDF backend breaks when the setting pdf.use14corefonts=True is
used. You'll find a test case reproducing this bug in the attached
file 'test_pdf_use14corefonts.py'.
This setting is very useful because it produces very lightweight PDF
files. The files are lightweight because they only use the 1
Nicolas Grilly writes:
> The PDF backend breaks when the setting pdf.use14corefonts=True is
> used. You'll find a test case reproducing this bug in the attached
> file 'test_pdf_use14corefonts.py'.
You're right. I committed your patch, but there is another bug that
makes this a little difficult
> I will have a look at the code for both PyGTK and OS X.
> Hopefully that will show me more of the best way of
> handling this.
The code in PyGTK is a bit easier to understand than the code for OS X. The OS
X code also includes stuff to handle SIGINTs (keyboard interrupts by ctrl-c),
which is
