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

List:       kde-bugs-dist
Subject:    [plasmashell] [Bug 348825] Tooltip renders weird on first show, looks good on subsequent ones.
From:       Thomas Lübking <thomas.luebking () gmail ! com>
Date:       2015-06-07 16:23:44
Message-ID: bug-348825-17878-rDaQVLC3JA () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=348825

--- Comment #9 from Thomas Lübking <thomas.luebking@gmail.com> ---
(In reply to Mark from comment #8)
> So everyone that uses this tooltip should implement client logic to prevent
> the bug i've shown in the video from occurring? Ouch!
> 
> I don't buy the argument of QML is the one that needs fixing (QML is the
> language, QtQuick is the toolkit, i suppose you meant QtQuick).

Whether language or interpreter, maybe even the plasma componets (loading &
rendering svg or so): whatever is to blame that

a) creating a QtQuick/QML window is dead slow (on the main thread!)
b) it maps before the scene is at least basically initialized

needs to be fixed.

Granted: the ToolTip *could* detect the first show (internally it uses some
static Plasma Dialog QQuickWindow) event and show it offscreen, wait 1-2
seconds, then hide it and show it in the desired position, but
a) that's just moving the workaround
b) that may induce further problems (ugly workarounds go into client code, not
library code) in case the client simply expects that "map here" means "map
here" and not "first map over there, then here a little later") - alternatively
the tooltip had to block on first invocation (and by a timer...).

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]