Bug 345349

Summary:	Rendering glitches in the designer of Qt Creator (possibly QQuickWidget)
Product:	[Plasma] Oxygen	Reporter:	jeremy
Component:	general	Assignee:	Hugo Pereira Da Costa <hugo.pereira.da.costa>
Status:	NEEDSINFO WAITINGFORINFO
Severity:	major	CC:	filipfila.kde, hugo.pereira.da.costa
Priority:	NOR
Version First Reported In:	5.2.1
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
URL:	http://imgur.com/STAxmxZ
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description jeremy 2015-03-20 06:52:52 UTC

The screen says it all.
This is probably not a Qt problem since this rendering glitch only happens with Oxygen (and Breeze too).

I tried to pinpoint the problem myself by looking at the Qt Creator and the Oxygen codebase myself, but I didn't have time to understand them enough to be able to fix the rendering.

I made a little Qt test app with a QQuickWidget embedded in it and it worked just fine, Oxygen and Breeze didn't have any problem rendering it *but* since like I said any other Qt style than Breeze and Oxygen will render Qt Creator just fine, I'm really confused about what and who is causing the problem exactly.

If someone can give me some /directions/, I can try again tomorrow to fix it.

Thanks,



Reproducible: Always

Comment 1 Hugo Pereira Da Costa 2015-03-20 07:28:40 UTC

Can you also post a screenshot of how it looks with another widget style ? Aside from the error messages, I am not quite sure what the rendering issue is. 
Also, if it happens inside Qt creator and not in a 'real' app, it might actually be related to Qt creator itself.

Comment 2 Hugo Pereira Da Costa 2015-03-20 07:30:16 UTC

(as a side note, and this also is due to Qt creator, there is pretty much nothing on the screenshot that looks like oxygen, so you better off using qtcreator -style plastique in the meanwhile :))

Comment 3 Hugo Pereira Da Costa 2015-03-20 07:31:44 UTC

Finally, any chance you can test a more recent version of Qt5 (5.4) ? I think to remember there have been 'fixes' on the QtQuickControls in there (but not 100% sure)

Comment 4 jeremy 2015-03-20 18:53:51 UTC

(In reply to Hugo Pereira Da Costa from comment #1)
> Can you also post a screenshot of how it looks with another widget style ?
> Aside from the error messages, I am not quite sure what the rendering issue
> is. 
> Also, if it happens inside Qt creator and not in a 'real' app, it might
> actually be related to Qt creator itself.

http://i.imgur.com/uhbVuz0.png

What do you mean when you say a "real app"?
Do you say that because Qt Creator looks to be using a custom style itself? 

From what I understand, widgets with black rendering are QQuickWidget and Oxygen is making them somehow "native" ( http://doc.qt.io/qt-5/qwidget.html#native-widgets-vs-alien-widgets ).

And QQuickWidget can't be rendered as native widget or else it doesn't render at all ( https://qt.gitorious.org/qt/qtdeclarative/source/c9553ad7d8041c7b0fd769dc8cd0f5335d9408a3:src/quickwidgets/qquickwidget.cpp#L770 )

Comment 5 jeremy 2015-03-20 18:55:29 UTC

(In reply to Hugo Pereira Da Costa from comment #3)
> Finally, any chance you can test a more recent version of Qt5 (5.4) ? I
> think to remember there have been 'fixes' on the QtQuickControls in there
> (but not 100% sure)

I have Qt-5.4.1

Comment 6 jeremy 2015-03-22 11:12:08 UTC

Tried again with the QtCurve theme and its working just fine too: https://www.archlinux.org/packages/community/x86_64/qtcurve-qt5/

Maybe there is something wrong with KStyle ?

Comment 7 Hugo Pereira Da Costa 2015-03-22 12:52:57 UTC

If you feel like testing this (I have had no time for testing myself), you can just change the ifdef's in breezestyle.h (look for ParentStyleClass). 

Thanks ! 

Hugo

Comment 8 Justin Zobel 2021-03-09 23:58:18 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.

Comment 9 Filip Fila 2026-02-13 08:15:47 UTC

Please provide an update if you're still affected by this.