On Sat, Aug 23, 2014 at 12:40 PM, David Narvaez
wrote:
> I was ready to create my bug report with sample code etc, and came across
>
> https://bugreports.qt-project.org/browse/QTBUG-26358
>
> which seems to be related because I was able to confirm paintEvent is
> not called with this flag set. Cou
On Wed, Aug 20, 2014 at 12:17 PM, David Narvaez
wrote:
> On Thu, Aug 14, 2014 at 12:34 PM, Shaw Andy wrote:
>> If you were using WA_PaintOnScreen then you also need to ensure you
>> reimplement paintEngine() to return 0. Had you done that at all?
>
> Thanks for your help and sorry for the late r
On Thu, Aug 14, 2014 at 12:34 PM, Shaw Andy wrote:
> If you were using WA_PaintOnScreen then you also need to ensure you
> reimplement paintEngine() to return 0. Had you done that at all?
Thanks for your help and sorry for the late reply. I was missing the
return 0 on paintEngine() (I should hav
> > I am porting an application to Qt5/KF5 and was surprised to see the
> > main widget of the application was showing all black. There are
> > screenshots of the original version and the buggy version[1] online. I
> > removed
> >
> > setAttribute( Qt::WA_PaintOnScreen, true );
> >
> > on that widg
Hi
>
> I am porting an application to Qt5/KF5 and was surprised to see the
> main widget of the application was showing all black. There are
> screenshots of the original version and the buggy version[1] online. I
> removed
>
> setAttribute( Qt::WA_PaintOnScreen, true );
>
> on that widget and t
Hi,
I am porting an application to Qt5/KF5 and was surprised to see the
main widget of the application was showing all black. There are
screenshots of the original version and the buggy version[1] online. I
removed
setAttribute( Qt::WA_PaintOnScreen, true );
on that widget and the widget was ren
