matplotlib-devel Mailing List for matplotlib

This is a good suggestion.

I've committed your patch (with a slight modification so it works with 
the STIX fonts also) in SVN r7944 and r7645.

Thanks, and more patches always welcome!

Mike

Sean Arms wrote:
> Greetings,
>
> I've been checking out the code in lib/matplotlib/mathtext.py with the
> hope of adding support for a "widebar".  I have something that works,
> although unlike \widetilde and \widehat, I can only find one glyph and
> it's in cmr10.  I've attached a patch that adds \widebar support using
> svn rev 7943 if anyone is interested!
>
> Cheers!
>
> Sean Arms
> University of Oklahoma
> School of Meteorology
> PhD Candidate
>
> Index: lib/matplotlib/mathtext.py
> ===================================================================
> --- lib/matplotlib/mathtext.py  (revision 7943)
> +++ lib/matplotlib/mathtext.py  (working copy)
> @@ -769,6 +769,7 @@
>                         ('ex', '\x64')],
>         r'\widetilde': [('rm', '\x7e'), ('ex', '\x65'), ('ex', '\x66'),
>                         ('ex', '\x67')],
> +        r'\widebar'  : [('rm', '\xB9')],
>         r'<'         : [('cal', 'h'), ('ex', 'D')],
>         r'>'         : [('cal', 'i'), ('ex', 'E')]
>         }
> @@ -2481,7 +2482,7 @@
>         r'overleftarrow'  : r'\leftarrow'
>         }
>
> -    _wide_accents = set(r"widehat widetilde".split())
> +    _wide_accents = set(r"widehat widetilde  widebar".split())
>
>     def accent(self, s, loc, toks):
>         assert(len(toks)==1)
>   
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>   

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

On Wed, Nov 4, 2009 at 5:29 PM, Pierre Raybaut <co...@py...> wrote:
> A simpler fix would be:
>
>        class FigureWindow(QtGui.QMainWindow):
>            def __init__(self):
>                super(FigureWindow, self).__init__()
>
>            def closeEvent(self, event):
>                super(FigureWindow, self).closeEvent(event)
>                self.emit(QtCore.SIGNAL('destroyed()'))
>
> and replacing QtGui.QMainWindow by FigureWindow in FigureManagerQT.

I am pretty sure this is not caused by matplotlib, but rather a
regression in PyQt4 that will be fixed in the next release. There is a
post on the PyQt mailing list titled "Regressions on destruction of
objects?" and a note in the development snapshots changelog. If I try
your example with PyQt4-4.5.4, it works fine, but it crashes with
4.6.1. I will revisit the issue once PyQt4-4.7 is released.

Darren

Greetings,

I've been checking out the code in lib/matplotlib/mathtext.py with the
hope of adding support for a "widebar".  I have something that works,
although unlike \widetilde and \widehat, I can only find one glyph and
it's in cmr10.  I've attached a patch that adds \widebar support using
svn rev 7943 if anyone is interested!

Cheers!

Sean Arms
University of Oklahoma
School of Meteorology
PhD Candidate

Index: lib/matplotlib/mathtext.py
===================================================================
--- lib/matplotlib/mathtext.py  (revision 7943)
+++ lib/matplotlib/mathtext.py  (working copy)
@@ -769,6 +769,7 @@
                        ('ex', '\x64')],
        r'\widetilde': [('rm', '\x7e'), ('ex', '\x65'), ('ex', '\x66'),
                        ('ex', '\x67')],
+        r'\widebar'  : [('rm', '\xB9')],
        r'<'         : [('cal', 'h'), ('ex', 'D')],
        r'>'         : [('cal', 'i'), ('ex', 'E')]
        }
@@ -2481,7 +2482,7 @@
        r'overleftarrow'  : r'\leftarrow'
        }

-    _wide_accents = set(r"widehat widetilde".split())
+    _wide_accents = set(r"widehat widetilde  widebar".split())

    def accent(self, s, loc, toks):
        assert(len(toks)==1)

Hi Pierre,

Thanks for the report. I'll have a look as soon as I get a chance.

Darren

On Wed, Nov 4, 2009 at 5:29 PM, Pierre Raybaut <co...@py...> wrote:
> A simpler fix would be:
>
>        class FigureWindow(QtGui.QMainWindow):
>            def __init__(self):
>                super(FigureWindow, self).__init__()
>
>            def closeEvent(self, event):
>                super(FigureWindow, self).closeEvent(event)
>                self.emit(QtCore.SIGNAL('destroyed()'))
>
> and replacing QtGui.QMainWindow by FigureWindow in FigureManagerQT.
>
> Pierre
>
> Pierre Raybaut a écrit :
>> Hi,
>>
>> Some Spyder users have reported a critical bug occuring with
>> matplotlib 0.99's Qt4 backend and PyQt4 v4.6 (e.g. in Ubuntu Karmic).
>>
>>
>> Here is the traceback after calling 'plot([])', closing figure and
>> calling again 'plot([])' (e.g. in an IPython session with options
>> --pylab and --q4thread):
>>
>> Traceback (most recent call last):
>>  File "/home/rick/Temp/untitled0.py", line 9, in <module>
>>    show()
>>  File "/usr/lib/pymodules/python2.6/matplotlib/backends/backend_qt4.py",
>> line 63, in show
>>    manager.window.show()
>> RuntimeError: underlying C/C++ object has been deleted
>>
>>
>> I found out that the 'destroyed()' signal (connected in class
>> FigureManagerQT) is never emitted when figure is closed.
>> As a consequence, SIP is not very happy when trying to draw a deleted
>> object...
>>
>> I made the following changes to make it work:
>>
>> # New class to clarify code in FigureManagerQT
>> class FigureWindow(QtGui.QMainWindow):
>>    def __init__(self, num, canvas, close_callback):
>>        super(FigureWindow, self).__init__()
>>        self.close_callback = close_callback
>>        self.setAttribute(QtCore.Qt.WA_DeleteOnClose)
>>        self.setWindowTitle("Figure %d" % num)
>>        image = os.path.join(matplotlib.rcParams['datapath'],
>>                             'images', 'matplotlib.png')
>>        self.setWindowIcon(QtGui.QIcon(image))
>>        self._destroying = False
>>        self.setCentralWidget(canvas)
>>        if matplotlib.is_interactive():
>>            self.show()
>>           def closeEvent(self, event):
>>        super(FigureWindow, self).closeEvent(event)
>>        self.close_callback()
>>
>> class FigureManagerQT( FigureManagerBase ):
>>    """
>>    Public attributes
>>
>>    canvas      : The FigureCanvas instance
>>    num         : The Figure number
>>    toolbar     : The qt.QToolBar
>>    window      : The qt.QMainWindow
>>    """
>>
>>    def __init__( self, canvas, num ):
>>        if DEBUG: print 'FigureManagerQT.%s' % fn_name()
>>        FigureManagerBase.__init__( self, canvas, num )
>>        self.canvas = canvas
>>
>>        # Give the keyboard focus to the figure instead of the manager
>>        self.canvas.setFocusPolicy( QtCore.Qt.ClickFocus )
>>        self.canvas.setFocus()
>>
>>        self.window = FigureWindow(num, self.canvas, self._widgetclosed)
>>        self.toolbar = self._get_toolbar(self.canvas, self.window)
>>        self.window.addToolBar(self.toolbar)
>>        QtCore.QObject.connect(self.toolbar, QtCore.SIGNAL("message"),
>>                               self.window.statusBar().showMessage)
>> # [...]
>>
>> And we may now remove the "QtCore.QObject.disconnect" for the no
>> longer existing signal 'destroyed()' in method 'FigureManagerQT.
>> destroy'.
>>
>> HTH
>>
>> Cheers,
>> Pierre
>>
>>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

On Tue, Nov 3, 2009 at 11:28 AM, Fernando Perez <fpe...@gm...> wrote:

> if you reside in the San Francisco Bay Area, you may be interested in
> a meeting we'll be having tomorrow November 4 (2-4 pm), as part of our
> regular py4science meeting series.  Guido van Rossum, the creator of
> the Python language, will visit for a session where we will first do a
> very rapid overview of a number of scientific projects that use Python
> (in a lightning talk format) and then we will have an open discussion
> with Guido with hopefully interesting questions going in both
> directions.  The meeting is open to all, bring your questions!

Video of the event:
http://www.archive.org/details/ucb_py4science_2009_11_04_Guido_van_Rossum

Slides: http://fperez.org/py4science/2009_guido_ucb/index.html

A few blog posts about it:

- Guido: http://neopythonic.blogspot.com/2009/11/python-in-scientific-world.html

- Jarrod: http://jarrodmillman.blogspot.com/2009/11/visit-from-guido-van-rossum.html

- Matthew: http://nipyworld.blogspot.com/2009/11/guido-van-rossum-talks-about-python-3.html

- Me: http://fdoperez.blogspot.com/2009/11/guido-van-rossum-at-uc-berkeleys.html

Attendance was excellent (standing room only, and I saw some people
leave because it was too full). Many thanks to all the presenters!

Cheers,

f