Version: 4.0 (using KDE 4.5.1) OS: Linux As late as KDE 4.5.1 (Have not been able to try 4.5.67) The KDE help tooltips (the one that comes up when you click on the help button in the title bar, and select an element) These tooltips still have the "single color with the black border" look that normal tooltips had in Oxygen in KDE 4.4 and below. There also is a hatched shadow underneath these tooltips as well. This shadow even appears if compositing is enabled. This is an inconstancy in the oxygen feel. Reproducible: Didn't try Steps to Reproduce: On a KDE application's window that has the help button on its title bar, click on that, and then get the help tooltip to appear on an element that has a description Actual Results: A tooltip comes up, with the description of the element, but in a tooltip that does not look like its part of the oxygen style Expected Results: Perhaps a tooltip that looks more like the ones that come up when you hover over an element in KDE 4.5, with a gradient, and without a hatched shadow, as KWIN compositing should add the shadow instead.
These "tooltips" are actually the "what's this" dialogs (as other OS names them). The inconsistency (which I fully aknowledge, and regret), is that Qt gives absolutely no hook for the style to customize the appearance of these. So there is practically nothing I can do about it. (if you check other styles no matter how fancy they are, these tooltips will always have the same appearance). There have been discussions on IRC on whether one can entirely bypass the widget, and create our (nice-looking) own widget instead. But that a bit outside the scope of a widget style. No ? I'll be looking at this solution though. In the meanwhile I close as Upstream, cause really, this is a Qt bug (and the more people report to them, the more likely it is that they fix it). Hugo
PS: sorry for my english. I guess I have been typing too fast.
QTBUG-1444 (unfortunately "out of scope" without any reason).
@Christoph Then I guess that there is no other option that capture the relevant events and re-implement the whole thing (from what I could see in the code, this looks doable, although quite 'out-of-scope' too ;) )
damn. My english is really bad today