handling dialogs

Aaron J. Seigo aseigo at kde.org
Sat Jan 12 06:26:12 CET 2008


hi all..

random brain dump follows as i mull over an annoying problem:

right now we have a general purpose problem: a dialog in plasma that is 
already visible, when called again but while on another desktop, needs to 
have KWindowSystem::setOnDesktop and KWindowSystem::activateWindow called on 
it to make sure that it actually pops.

i considered extending Plasma::Dialog and implementing a showEvent handler as 
well as making the SVG panel drawing optional ... but this doesn't cover 
cases where people make the full dialog in designer (well, they shoudl only 
be making QWidgets and putting them in KDialogs, but still) nor does it cover 
the use case where we are using dialogs from external sources ...

trying to catch every show() event of a dialog is not overly easy. it's also 
not appropriate for every user of libplasma. so it's probably something that 
needs to happen in the plasma app itself. i've considered implementing 
QApplication::x11EventFilter but that seems a little heavy handed.

i'm not fond of having to catch every place a dialog isn't being properly 
managed either.

blarg.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/panel-devel/attachments/20080111/28325f2d/attachment.pgp 


More information about the Panel-devel mailing list