[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyQt] QNetworkReply pyQt
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2017-05-03 18:04:47
Message-ID: CAExHGmR1xGhHfzjR1__kiycL47g-w5xvALwp1fRh79stTydLuA () mail ! gmail ! com
[Download RAW message or body]

Hi,

On Wed, May 3, 2017 at 6:07 PM, Andreas Pakulat <apaku@gmx.de> wrote:
> Hi,
>
> On Wed, May 3, 2017 at 5:33 PM, Florian Bruhin <me@the-compiler.org> wrote:
>> Hi,
>>
>> On Wed, May 03, 2017 at 10:53:37AM -0400, Christopher Probst wrote:
>>> Problem is, it looks as if the readyRead, error or finished signal are
>>> never emitted. What am I doing wrong?
>>
>> Hard to say without a working example - I think it'd also be possible
>> that the readyRead signal is emitted before you connect the slot. Then
>> it's never emitted again (and neither are the others) because you never
>> read anything from the reply.
>
> The behavior of at least the finished signal has recently been
> discussed on the qt list. Since using a QNetworkReply in the way the
> OP does is perfectly valid its guaranteed by Qt that the 'finished'
> signal is always emitted even if you connect it after you 'started'
> the network request. So in the scenario outlined at least the finished
> signal should be emitted for sure.

For reference this is the thread on the Qt mailinglist:

http://lists.qt-project.org/pipermail/interest/2017-April/026862.html

Andreas
_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread]