---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/115001/
---
(Updated Jan. 16, 2014, 6:06 p.m.)
Status
--
This change has been
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/115001/#review47338
---
given that the framework installs into KF5GlobalAccel and has
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/115001/#review47339
---
Wouldn't that break KDElibs4 applications talking to
Wouldn't that break KDElibs4 applications talking to kglobalacceld from KF5?
- Martin Gräßlin
Yes it would. There can be only one kglobalaccel. If its from kde4 or kde4
shouldn't matter so it HAS to keep dbus compatibility.
On Jan. 13, 2014, 6:03 p.m., Martin Gräßlin wrote:
Wouldn't that break KDElibs4 applications talking to kglobalacceld from KF5?
On Montag, 13. Januar 2014 19:24:12 CEST, Michael Jansen wrote:
Yes it would. There can be only one kglobalaccel. If its from kde4 or kde4
shouldn't matter so it
On Jan. 13, 2014, 6:03 p.m., Martin Gräßlin wrote:
Wouldn't that break KDElibs4 applications talking to kglobalacceld from KF5?
Thomas Lübking wrote:
On Montag, 13. Januar 2014 19:24:12 CEST, Michael Jansen wrote:
Yes it would. There can be only one kglobalaccel. If its from
On Jan. 13, 2014, 6:03 p.m., Martin Gräßlin wrote:
Wouldn't that break KDElibs4 applications talking to kglobalacceld from KF5?
Thomas Lübking wrote:
On Montag, 13. Januar 2014 19:24:12 CEST, Michael Jansen wrote:
Yes it would. There can be only one kglobalaccel. If its from
