https://bugs.kde.org/show_bug.cgi?id=498913
--- Comment #9 from Jakob Petsovits <jpe...@petsovits.com> --- So, to backtrack to the original bug report: At which point would we consider this bug closed? - Once the 1-second delay is configurable via powerdevilrc? - Once the 1-second delay is configurable via UI? - Once `--disable-cross-instance-locks` is configurable via UI? (Note that powerdevil will already use any existing ddcutilrc.) - All of the above? > As a bonus, if it's possible to cache and use the `--bus` arg when opening > monitor handles with libddcutil, it may speed it up as mentioned in the docs > below. Using this with ddcutil cli reduces update time by over 50%. I'm not sure about that, because we only initialize libddcutil once at session startup and then it just keeps running. The ddcutil CLI needs to re-initialize it every time, so caching would make sense there, but if it's never closed then we don't need to remember any `--bus` value? Or am I missing something? -- You are receiving this mail because: You are watching all bug changes.
