On 26-Apr-01 Phil Thompson wrote:
>>===== Original Message From <[EMAIL PROTECTED]> =====
>>I consistently get the following warning using
>>Py[Qt,KDE] 2.3 or 2.4:
>> QObject::connect: Incompatible sender/receiver arguments
>> QSignal::x() --> sipProxyqt::proxySlot(int)
> It is probably a bug in PyQt, but only applies when compiling with Qt v1.x.
> PyQt should compile with such prehistoric versions of Qt, but I don't test it
> when making a new release.
> Do you really need to use such an old version?
Well, unless I'm thoroughly confused (which happens entirely too often), I need
Qt1.4x for PyKDE, and I'm assuming that the associated PyQt version needs to be
compiled with the same Qt lib version - am I mistaken there?
We just finally upgraded to KDE2 with the release of 2.1, so I've given the
whole situation some thought in the last few weeks and my conclusions are:
1. I don't want to switch to GTK (gack!)
2. I don't want to go back to C++ for this particular project
3. Using Qt, I also need some of the KDE widgets, like the HTML widget and
otheres (this is a very specialized MUA with lots of features we need but nobody
else would probably want)
4. Since there is no PyKDE2 (and I really don't need it that badly), Qt1.4x and
KDE1 should be just fine.
5. I don't expect the remaining problems related to Qt<2.2 and KDE<2 will get
much attention, and I think that's a fair situation
For this particular problem, there's probably an 'assert' somewhere in the Qt
source I can comment out if it gets too annoying, and since Qt1.4x isn't
supporting much else I use, I don't feel too bad about doing that. Just thought
someone might know of a fix other than patching the Qt source.
I'm always impressed by your quick responses, and really appreciate the effort
you've put in to PyQt and PyKDE.
Thanks!
Jim Bublitz
_______________________________________________
PyKDE mailing list [EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde
