Review Request 120243: Remove fallback QSystemTray support
David Edmundson
david at davidedmundson.co.uk
Wed Sep 17 13:01:28 UTC 2014
> On Sept. 17, 2014, 12:55 p.m., Aleix Pol Gonzalez wrote:
> > Maybe we want to ifdef it? We won't require Qt 5.4 in a while...
It doesn't require Qt5.4.
- David
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120243/#review66738
-----------------------------------------------------------
On Sept. 17, 2014, 12:07 p.m., David Edmundson wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/120243/
> -----------------------------------------------------------
>
> (Updated Sept. 17, 2014, 12:07 p.m.)
>
>
> Review request for KDE Frameworks.
>
>
> Repository: knotifications
>
>
> Description
> -------
>
> Remove fallback QSystemTray support
>
> Currently when we make a StatusNotifierItem if it fails we try to create
> a classic X system tray icon via Qt's QSystemTray.
>
> QSystemTray now (5.4) has a QPT backend that uses KStatusNotifierItem. This
> means it's possible to infinite loop.
>
> This patch removes the legacy QSystemTray support to avoid that
> happening.
>
> Downside: it means if a frameworks app is run on a platform without statusnotifier support but still has legacy X system tray support we would now gets no icons, but that would break on Wayland anyway.
>
>
> Diffs
> -----
>
> src/kstatusnotifieritem.h 7da1451
> src/kstatusnotifieritem.cpp 767537d
> src/kstatusnotifieritemprivate_p.h 051cc38
>
> Diff: https://git.reviewboard.kde.org/r/120243/diff/
>
>
> Testing
> -------
>
> Ran statusnotifiertest (the one in plasma-workspace) with plasma running. Everything is fine.
> Ran without plasma running and nothing happened (without kded5 infinite looping)
>
>
> Thanks,
>
> David Edmundson
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20140917/4e487ab0/attachment.html>
More information about the Kde-frameworks-devel
mailing list