----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/125028/#review84792 -----------------------------------------------------------
Have you tested this? Does the notification work with the zero timer? dataengines/time/timeengine.cpp (line 30) <https://git.reviewboard.kde.org/r/125028/#comment58687> I guess this could/should be removed dataengines/time/timeengine.cpp (line 69) <https://git.reviewboard.kde.org/r/125028/#comment58688> Should this maybe also set TFD_NONBLOCK? To avoid blocking calls? - Martin Klapetek On Sept. 3, 2015, 11:36 a.m., David Edmundson wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/125028/ > ----------------------------------------------------------- > > (Updated Sept. 3, 2015, 11:36 a.m.) > > > Review request for Plasma. > > > Repository: plasma-workspace > > > Description > ------- > > At the moment we update the clock when we resume from suspend or from > the time KCM. > > However the signal from the clock KCM isn't very good as it signals just > after it requests an NTP update or clock change, not necessarily when > that finishes. > > Also we miss any external NTP updates which might occur at other times > throughout the day, such as a big change when we connect to the network > > This method also avoids needing solid to tell us when we're resuming > from suspend, which is deprecated API and also seems slightly slower. > > BUG: 344870 > > > Diffs > ----- > > dataengines/time/timeengine.cpp 2fd9792209ff5e78bd3dee1ed938eb0b1173de8d > > Diff: https://git.reviewboard.kde.org/r/125028/diff/ > > > Testing > ------- > > > Thanks, > > David Edmundson > >
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel