> On Sept. 2, 2015, 2:35 p.m., Martin Klapetek wrote: > > But the ktimezoned should do exactly that; it monitors various files which > > timedate modifies and then sends that signal. Does ktimezoned not work in > > that case (it did when I last test it)? I think better place for this > > signal watcher would be in ktimezoned itself actually. > > Martin Klapetek wrote: > Edit: timedatectl set-timezone Europe/Prague changes my clock > immediatelly, so does "echo "Europe/Prague" > /etc/timezone
you are correct. I can kill one of the two signals because of my other patch, but I'll merged that into there. - David ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/125029/#review84766 ----------------------------------------------------------- On Sept. 2, 2015, 10:33 a.m., David Edmundson wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/125029/ > ----------------------------------------------------------- > > (Updated Sept. 2, 2015, 10:33 a.m.) > > > Review request for Plasma. > > > Repository: plasma-workspace > > > Description > ------- > > This means we get update the UI immedidately if the timezone is changed > from an external source, such as timedatectl or some user script based > on location for example. > > This patch would put more of a dependency on timedated..unless we > monitor both? > > CCBUG: 351008 > > > Diffs > ----- > > dataengines/time/timeengine.cpp 2fd9792209ff5e78bd3dee1ed938eb0b1173de8d > > Diff: https://git.reviewboard.kde.org/r/125029/diff/ > > > Testing > ------- > > > Thanks, > > David Edmundson > >
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
