On 19.12.06 10:45:21, Sibylle Koczian wrote: > Am Sonntag, den 17.12.2006, 19:33 +0100 schrieb Andreas Pakulat: > > > You should update that. PyQt4 4.0.1 doesn't have support for Qt4.2 > > Actually I'm surprised they got it to build with Qt4.2, IIRC the changes > > needed are only included in PyQt4 4.1. Thats one of the reasons I roll > > my own Python/Qt4/PyQt4 into $HOME here... > > > I'll probably have to do that too (or possibly find a distribution with > the newest Python/Qt4/PyQt4).
Hehe, Gentoo would be a good candidate ;) > > > > If you can't change your Qt version, try emitting the dataChanged > > > > Signal with the top-left and bottom-right QModelIndex. > > > > > > That has helped: I replaced the "self.reset()" at the end of > > > setResultset() with the dataChanged Signal, now I get the original data > > > back without changing focus or doing other tricks. It's not very > > > beautiful, but it works for the moment. > > > > This would imply that it could be a problem in Qt4.2.0 itself. Maybe you > > know enough C++ to re-write your example in it, just for testing of > > course. It seems its fixed in later Qt4.2 versions... > > It might be a good idea to relearn C++, but that will take time. Then I guess it's not worth the effort. I would've ported it myself, but I don't have time for such things at the moment. As its fixed in the current version of Qt4/PyQt4 there's no important reason for you to go back to that "strange" language called C++ ;) Andreas -- Reply hazy, ask again later. _______________________________________________ PyKDE mailing list [email protected] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
