Re: Review Request 119701: Fix bug #334271 : bad display of Dolphin status bar wdgets when a high DPI resolution is used

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119701/ --- (Updated août 12, 2014, 5:28 matin) Review request for Dolphin and KDE Ba

Re: Review Request 117174: Fix installing and removing desktop plasma theme packages.

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/117174/ --- (Updated Aug. 11, 2014, 6:58 p.m.) Status -- This change has been ma

Re: Killing kdelibs master branch

On 11/08/14 00:23:15, Albert Astals Cid wrote: > Any objection? None from me. That would make it clear for everybody that the applications should start using KF5. > > Cheers, > Albert

Review Request 119711: Use CMAKE_INSTALL_FULL_LIBEXECDIR_KF5

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119711/ --- Review request for kdelibs and David Faure. Repository: kinit Descripti

Re: Review Request 119701: Fix bug #334271 : bad display of Dolphin status bar wdgets when a high DPI resolution is used

> On Aug. 11, 2014, 2:17 a.m., Christoph Feck wrote: > > dolphin/src/statusbar/dolphinstatusbar.cpp, line 120 > > > > > > Where does the text for the spaceInfo come from? If it is possible to > > compute the wid

Re: Review Request 119663: libkscreensaver: blank mouse cursor in startup code

> On Aug. 8, 2014, 3:35 nachm., Thomas Lübking wrote: > > Would it be sufficient to set the cursor on "target" instead of an > > application wide override? > > > > setOverrideCursor has this "nasty" stack behavior which could be > > troublesome in a library and I could eg. think of "screensave

Re: Review Request 119701: Fix bug #334271 : bad display of Dolphin status bar wdgets when a high DPI resolution is used

> On Aug. 11, 2014, 12:17 vorm., Christoph Feck wrote: > > dolphin/src/statusbar/dolphinstatusbar.cpp, line 120 > > > > > > Where does the text for the spaceInfo come from? If it is possible to > > compute the w

Re: Review Request 119663: libkscreensaver: blank mouse cursor in startup code

> On Aug. 8, 2014, 5:35 nachm., Thomas Lübking wrote: > > Would it be sufficient to set the cursor on "target" instead of an > > application wide override? > > > > setOverrideCursor has this "nasty" stack behavior which could be > > troublesome in a library and I could eg. think of "screensave