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

List:       pykde
Subject:    Re: [PyQt] Can't connect to QWebEnginePage::renderProcessTerminated
From:       Phil Thompson <phil () riverbankcomputing ! com>
Date:       2017-02-09 22:29:46
Message-ID: E5FFA42E-79C9-49AE-B0FB-A5B1A2594652 () riverbankcomputing ! com
[Download RAW message or body]

On 9 Feb 2017, at 9:26 pm, Florian Bruhin <me@the-compiler.org> wrote:
> 
> * Phil Thompson <phil@riverbankcomputing.com> [2017-02-06 17:12:52 +0000]:
> > On 6 Feb 2017, at 4:50 pm, Florian Bruhin <me@the-compiler.org> wrote:
> > > 
> > > Hi,
> > > 
> > > I tried various ways of connecting to
> > > QWebEnginePage.renderProcessTerminated (see the attached file), but
> > > they all fail with:
> > > 
> > > 	QObject::connect: No such signal \
> > > QWebEnginePage::renderProcessTerminated(QWebEnginePage::RenderProcessTerminationStatus,int)
> > >   Traceback (most recent call last):
> > > 	  File "render.py", line 23, in <module>
> > > 		page.renderProcessTerminated.connect(obj.slot1)
> > > 	TypeError: connect() failed between \
> > > renderProcessTerminated(QWebEnginePage::RenderProcessTerminationStatus,int) and \
> > > unislot()
> > 
> > I reported this as a Qt bug nearly a year ago. I'll chase it up.
> > Otherwise I might build in a workaround for future releases.
> 
> I'm guessing it's this? https://codereview.qt-project.org/#/c/185148/
> 
> Looks like the fix was abandoned because it's backwards-incompatible
> though.

I've suggested a compatible fix would be to add an overload for the signal.

> At least connecting to the view's signal works, but I think it'd be
> good if PyQt had a workaround for this if Qt can't fix it.

I think I'll do this anyway - but not for PyQt v5.8.

Phil
_______________________________________________
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]