Phil Thompson-5 wrote:
>
>>I had to replace
>> ImageLink arguments in signal definition with 'PyQt_PyObject', not sure
>>why exactly)
>
> Neither am I.
>
Else I would get the following message:
> TypeError: type 'classobj' is not supported as a pyqtSignal() type
> argument type
>
which is
Hi Phil,
thanks for the detailed explanation, although I have to admit I have a bit
of a hard time following through.. Anyway...
Phil Thompson-5 wrote:
>
> I've already suggested that you should simplify your ImageLink class so
> that it does not derive from QObject.
>
Okay but there must be
Hi Phill, Hans,
thanks a lot for your answers.
Hans-Peter Jansen-2 wrote:
>
> This does NOT qualify as a small piece of code, because:
> - it's convoluted code (e.g. it's not obvious, which part runs threaded)
> - you're doing hard to track things with QUrls (this is, where it
> crashes)
>
Phil Thompson-5 wrote:
>
> Either way people need a small, self-contained example that demonstrates
> the problem.
>
Hi Phil,
I think I've been able to isolate a small piece of code that consistently
reproduces the problem. http://old.nabble.com/file/p26619445/main.py This
piece of code dis
Hi there,
so what should I do about this issue? Should I file a bug report? Or is it
only me? The PyQt4 version I'm using is fairly recent however it crashes A
LOT! What gives?
Thanks for your help,
Chris
--
View this message in context:
http://old.nabble.com/Freezes-and-crashes-with-signal-a
Hi Phil,
Phil Thompson-5 wrote:
>
> I thought you were using current snapshots (where the code that was
> crashing was only compiled in with old versions of Qt).
>
I've just tried against the latest snapshots
(sip-4.9.2-snapshot-20091115.tar.gz and
PyQt-x11-gpl-4.6.2-snapshot-20091115.tar.gz
Hi Phil,
Phil Thompson-5 wrote:
>
> It's difficult to see how this would crash if everything else (ie. Python
> and Qt) is working as it should.
>
> However it does imply you are using a very old version of Qt (v4.1).
>
what leads you to think to an old version is used ? In fact this should
Hi again;
Phil Thompson-5 wrote:
>
> I can't remember if you are using snapshots or not, but there are some
> issues fixed related to looking up Python reimplementations of virtual
> methods.
>
forget about Windows. The whole thing crashes so quick on Windows XP that I
can't even get a glimps
Hi again!
Phil Thompson-5 wrote:
>
> If you have a list of the QThread instances you can scan the list when
> finished() is received to see which one it is. There is an obvious race
> condition with that approach.
>
I don't know if this race condition is obvious but I'm personally unable to
i
Phil Thompson-5 wrote:
>
>
> I think this is all one problem and is nothing to do with threads. There
> is
> a (necessary) change of behaviour (documented in the current snapshot)
> when
> wrapping a Python sub-class of a QObject in a QVariant.
>
> Previously this was first wrapped in a PyQt_P
Phil Thompson-5 wrote:
>
> Can you try with the latest installer (though it does contain a nasty
> thread-related regression).
>
> Do you have a test case?
>
> Phil
>
Hi Phil,
I'm currently using PyQt 4.6-1 with Python 2.6.3. I think I've been able to
isolate a http://www.nabble.com/file/p
Hi there,
I'm having some problems with a fairly simple multi-threaded application
under PyQt 4.5.4 and Windows XP. I have a number of worker threads that feed
one consumer in the main GUI thread. Initially I had the worker threads
directly call the "add" method of the consumer object; this piece
12 matches
Mail list logo
