Hi Ben, Hi list, > Exactly. That's all I found too. Nothing indicates that we need to > change anything. We are throwing away the second part of the tuple > which has the returned filter. The only reason I see for the new > function is so the coder can get back the filter string, which we > don't seem to use.
It took me a while to see the problem, too. The point is: there is one parameter missing in the new API of getSaveFileName, called selectedFilter, which we use, and given that it is missing, python takes it to be the next parameter, which must be an int, and you get a TypeError. I discussed this with Phil Thompson (the author of PyQt4) over at the PyQt4 mailing list (see http://www.mail-archive.com/pyqt%40riverbankcomputing.com/msg23733.html) and he told me to use getSaveFileNameAndFilter. The other option would be to change PyQt4, dunno which is best. Greetings Martin -- Max-Born-Institut Max-Born-Straße 2a 12489 Berlin +49 30 6392 1234 ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
