On Monday 06 April 2009, Marco Martin wrote: > Hi all, > i'm pretty happy about the state of the new systray implementation, i would > say the client library it's mostly ready for review, the only big problem > it has now is the following: > when the context menu is shown it is necessary to click on it (even on the > borders of the menu not necessarly an action) to make it go away, or > alternatively on the application main widget (doesn't change anything if > it's the parent of the menu or not) > it also refuses any sort of keyboard input, unless the main widget is > visible and focused. > does somebody have an idea?
i wonder if calling setFocus on it before exec would help any? also, there's a default menu created and passed to setContextMenu. that's cool, except that if setContextMenu is called again, say by the application, to customize that menu then the first menu will just dangle until the notification item is deleted. so not really a memory leak, per se, but i wonder if it shouldn't be deleted if a custom menu is set? -- 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 Qt Software
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
