Michiel De Hoon c2b2.columbia.edu> writes:
>
> I believe that this is because the QFile object as implemented in the Qt
> library on which PyQT builds does not emit the readyRead signal either. See:
>
> http://doc.trolltech.com/4.3/qfile.html
QFile inherits QIODevise that has such a signal. Bu
I believe that this is because the QFile object as implemented in the Qt
library on which PyQT builds does not emit the readyRead signal either. See:
http://doc.trolltech.com/4.3/qfile.html
As far as I can tell, there is no basic reason why a QFile should not emit a
readyRead signal. The analogou
Andreas Pakulat gmx.de> writes:
> And what exactly is "self"? You should try to come up with a small
> self-contained example.
Just a QWidget:
class MainWin(QtGui.QTextEdit):
def __init__(self, mapper, parent=None):
QtGui.QTextEdit.__init__(self, parent)
self.qsn = Qt
On 06.11.07 15:08:49, Vladimir Pouzanov wrote:
> Is there any way to read stdin line by line without blocking? My application
> receives data over stdin (one command per line) and should react immediately.
>
> I've tried to make such thing:
> self.stdin = QtCore.QFile(self)
> self.stdin.op
Is there any way to read stdin line by line without blocking? My application
receives data over stdin (one command per line) and should react immediately.
I've tried to make such thing:
self.stdin = QtCore.QFile(self)
self.stdin.open(0, QtCore.QIODevice.ReadOnly)
self.connect(self.stdi
On Tue, 06 Nov 2007 14:34:36 +, Phil Thompson wrote:
> I'm afraid you are on your own - or prove the problem exists without
> boost being in the picture.
what's the matter with boost? boost::python doesn't really interfere with
pyqt at all ... all classes are completely separate ... boost::p
On Tuesday 06 November 2007, Tim Blechmann wrote:
> >> i've upgraded to the latest debian packages of pyqt and sip (4.7.1).
> >> however i still experience the problem, described above ...
> >>
> >> is this issue known to be completely fixed?
> >
> > No bug is ever known to be fixed, only that it c
>> i've upgraded to the latest debian packages of pyqt and sip (4.7.1).
>> however i still experience the problem, described above ...
>>
>> is this issue known to be completely fixed?
>
> No bug is ever known to be fixed, only that it cannot be reproduced with
> current test cases. Have you got a
On Tuesday 06 November 2007, Tim Blechmann wrote:
> hi all,
>
> >>> > so, i had quite a number of crashes, with messages like:
> >>> >
> >>> > ASSERT failure in QCoreApplication::sendEvent: "Cannot send events
> >>> > to objects owned by a different thread. Current thread b022db50.
> >>> > Receiver
hi all,
>>> > so, i had quite a number of crashes, with messages like:
>>> >
>>> > ASSERT failure in QCoreApplication::sendEvent: "Cannot send events
>>> > to objects owned by a different thread. Current thread b022db50.
>>> > Receiver 'mainWindow' (of type 'QWidget') was created in thread
>>> > 8
10 matches
Mail list logo
