https://bugs.kde.org/show_bug.cgi?id=381173
--- Comment #6 from Mariusz Mazur <mariusz.g.ma...@gmail.com> ---
Ok, so I've rewritten the timer logic and now the plasmoid is (much more)
precise independently of issues with Qt. And fixed a few other bugs while I was
at it.
So first order of business is getting that code merged. Dealing with the Qt
bug, well, isn't really my priority, considering that (a) I don't want to spend
the time on learning how to build qt things and (b) if it's not just the qt
timer itself, but it interacting with something else in the plasmoid, then it
could take a while to pinpoint a test case. Especially for someone who has no
idea how to write plasmoids.
If anybody in here has a qt dev env and the know-how to use it to do a quick
test, then the offending code I'd start with would look something like this:
Timer {
id: t;
interval: 1000;
onTriggered: {
var ts = new Date().getTime();
console.log(ts);
}
repeat: true;
running: true;
}
What should happen is a log output roughly every second. What instead happened
in my debugging of the plasmoid was two log outputs every second, a few
milliseconds apart.
Which nicely explains why the plasmoid on my ubuntu 17.10 worked fine, and then
got the double boost when I upgraded to 18.04, all the while the code of the
plasmoid itself has not changed one bit. Only possible conclusion: the problem
must be in the underlying libraries.
--
You are receiving this mail because:
You are watching all bug changes.
