On Tuesday 22 January 2013 18.10:14 Vishesh Handa wrote: > > 1. Add an explicit Resource::setWatchEnabled( bool ) function in the > Resource class which clients can call if they want updates. > *
That's maybe safer in case there is still a client relying on that functionality.. > * > 2. Disable this automatic updating all together. > * ... but this is IMO the better design decision. So I'd suggest option 2. > * > *When should this be done? > The sooner the better, but something for the release-team to answer. I don't think it's that much of a problem that we absolutely have to get it into 4.10.0, is it? Cheers, Christian > * > I would like to do it in the 4.10 series. Maybe 4.10.1 or 4.10.0? But it > would involve adding a new public function. Otherwise there is always 4.11. > * > * > Currently, no applications depend on this "automatic-updating" behaviour of > the Resource class. Also, this behaviour was never advertised. > > Opinions? > > [1] https://codereview.qt-project.org/45163 _______________________________________________ Nepomuk mailing list [email protected] https://mail.kde.org/mailman/listinfo/nepomuk
