Hi, >> There's also always the possibility to reconsider implementing an >> Xcb-style >> alarm based mechanism that relies on a helper process, if it turns out >> in the >> future that KIdleTime/Mac is causing significant amounts of overhead. >> But >> KIdleTime has changed only minimally from KDE4 to KF5, and it is >> certainly not >> the case that it has led to any observable amount of continuous >> overhead until >> now. > > NO POLLING! Given your reply here, you did not even properly consider my > argument at all. Which is sad. I'm spending quite some time here to help > with the OSX implementation. I could also do a "what do I care about > OSX?" Instead I spent quite some time on it. I can only tell: Better no implementation than any polling implementation.
The idea of that framework is to give applications a "efficient" way to schedule stuff to do if idle (at least I thought so). Greetings Christoph -- ----------------------------- Dr.-Ing. Christoph Cullmann --------- AbsInt Angewandte Informatik GmbH Email: cullm...@absint.com Science Park 1 Tel: +49-681-38360-22 66123 Saarbrücken Fax: +49-681-38360-20 GERMANY WWW: http://www.AbsInt.com -------------------------------------------------------------------- Geschäftsführung: Dr.-Ing. Christian Ferdinand Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234 _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel