This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Tooltips of Qt applications in KDE

Tags: None
(comma "," separated)
pmzqla
Registered Member
Posts
5
Karma
0

Tooltips of Qt applications in KDE

Sun Oct 12, 2014 7:42 pm
Hi everybody,

I'm currently using KDE 4.14 and I have a question regarding tooltips in Qt applications. As you know, tooltips are by default rounded in KDE and it's usually the same for all the Qt applications. However, I have problems with one, qBittorrent.

When the compositing is enabled, tooltips in qBittorrent are not really rounded, they show white corners.

Here a screenshot:
Image

As soon as I disable the compositing, they are rounded as in every other application.

Is this a problem of qBittorrent or KDE? Does anyone know what can be done to have round tooltips?
Some hints would be helpful.

Thanks.
User avatar
google01103
Manager
Posts
6668
Karma
25
just guessing as I don't think I have any QT apps installed

you could try running: qtconfig -> Select Gui Style -> I would think Desktop Settings (Default)


OpenSuse Leap 42.1 x64, Plasma 5.x

pmzqla
Registered Member
Posts
5
Karma
0
Thanks for the reply.
Unfortunately things are already set the way you wrote and setting Oxygen from qtconfig has no effect on how tooltips are rendered.
luebking
Karma
0
that will be application specific (there's no "kde"/"qt" difference regarding the guistyle and tooltips)
qbittorrent will likely defeat argb windows, either by exporting XLIB_SKIP_ARGB_VISUALS=1 or by withdrawing the WA_Trans lucentBackground flag.
could also be an oxygen bug, this popped up in google:
http://web.archiveorange.com/archive/v/ ... HNVMNQ8VtS

ie. if that's a custom tooltip class, painted w/ the regular tip styling and the style doesn't test for the translucency flag.
pmzqla
Registered Member
Posts
5
Karma
0
luebking wrote:that will be application specific (there's no "kde"/"qt" difference regarding the guistyle and tooltips)
qbittorrent will likely defeat argb windows, either by exporting XLIB_SKIP_ARGB_VISUALS=1 or by withdrawing the WA_Trans lucentBackground flag.
could also be an oxygen bug, this popped up in google:
http://web.archiveorange.com/archive/v/ ... HNVMNQ8VtS

ie. if that's a custom tooltip class, painted w/ the regular tip styling and the style doesn't test for the translucency flag.


Interesting, starting qBittorrent with
Code: Select all
XLIB_SKIP_ARGB_VISUALS= qbittorrent  #doesn't matter what's the value of the variable

gets rid of the white corners. However, the round corners of the tooltips are pixelated (as when the compositing is disabled), but the shadow is correctly displayed.
Also, the tray icon (which is the logo of qBittorrent, hence a circle) is squared and the parts that should be transparent have the color of the background of the plasma theme (since the taskbar is translucent, there's a noticeable difference).

EDIT:
The same thing happens with every application I try.
luebking
Karma
0
You define the variable to somethig else than "0" - as a result you don't get ARGB visuals and instead the tooltip is masked (sicne the shape extension operates on bitmasks, it's aliased, ie. pixelated)

Do you have QtCurve, Bespin or Virtuality (styles) installed? Do you get white borders with them as well? (qbittorrent -style qtcurve)
pmzqla
Registered Member
Posts
5
Karma
0
luebking wrote:You define the variable to somethig else than "0" - as a result you don't get ARGB visuals and instead the tooltip is masked (sicne the shape extension operates on bitmasks, it's aliased, ie. pixelated)

I meant that even XLIB_SKIP_ARGB_VISUALS=0 qbittorrent does that, which is not what I'd expect.

Do you have QtCurve, Bespin or Virtuality (styles) installed? Do you get white borders with them as well? (qbittorrent -style qtcurve)

QtCurve doesn't have round tooltips, so I can't say if the issue is there or not, but Bespin does and they are displayed correctly in qBittorrent.
luebking
Karma
0
bugs.kde.org, please file a bug against oxygen/style.

I can confirm the weird XLIB_SKIP_ARGB_VISUALS behavior. I'm frankly not sure whether that is a recent regression or has always been this way (I probably never tried passing "0" or anything but "1") - unset'ting should still work, though.
pmzqla
Registered Member
Posts
5
Karma
0
Done: https://bugs.kde.org/show_bug.cgi?id=339939

Thank you for the support.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]