On Friday 26 June 2015 18:03:00 Frank Reininghaus wrote:
checking the mtime frequently can have a bad effect on the performance
though if it's done incorrectly. There is a bug report about high CPU
usage in Dolphin if sort by type is used:
https://bugs.kde.org/show_bug.cgi?id=346974
On Tuesday, July 14, 2015 11:49:25 AM David Faure wrote:
On Friday 26 June 2015 18:03:00 Frank Reininghaus wrote:
checking the mtime frequently can have a bad effect on the performance
though if it's done incorrectly. There is a bug report about high CPU
usage in Dolphin if sort by type is
On Monday 13 July 2015 23:14:17 Albert Astals Cid wrote:
I did a few tweaks, i still feel it seems this is the official way other
than an optional way of defining the version but maybe that's just me.
Hi, I have the same feeling as Albert that the current text is not clear
enough that both
On Tuesday 14 July 2015 19:28:58 Thomas Lübking wrote:
Actually, checking currentTime() is already the problem here (causing the IO
for the timezone stuff), see
http://marc.info/?l=kde-core-develm=143533622526705w=1 (the 1st paragraph
part of my comment somehow turned into a second-level
On Dienstag, 14. Juli 2015 19:00:14 CEST, Milian Wolff wrote:
On Tuesday, July 14, 2015 11:49:25 AM David Faure wrote:
On Friday 26 June 2015 18:03:00 Frank Reininghaus wrote: ...
It has. Querying the current time repeatedly is quite costly,
and often shows
up in code that extensively uses
