Mads Ipsen wrote: > It seems strange to me though, that something like this even can be an > issue, in the sense that it haven't been fixed ages ago. But maybe it > isn't as trivial as it looks?
I seem to recall it being a design issue, so it's hard to fix without breaking something else. Perhaps it's being addressed in Qt5. I'm not sure what the workaround is. Jeremy -- http://www.jeremysanders.net/ _______________________________________________ PyQt mailing list PyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
