classification as idle should start when idle begins, not when it reaches a threshold about arbtt

[nomeata]

Original comment by amenthes (Bitbucket: amenthes, GitHub: amenthes).

---

[nomeata]

Original comment by nomeata (Bitbucket: nomeata, GitHub: nomeata).

---

Indeed I believe that originally, I had this semantics for idle in mind, and a while the code was actually able to in principle look ahead and behind. But it was quite costly to do so, so at some point I dropped the possibility, analysing each sample on its own.

Furthermore, the $idle tag is not built: It is just a custom tag that you can define in your categorize.cfg. This also stands in the way of a more advanced calculation (unless that is made very general as well).

Also note that even with a tighter interpretation of idle, it will never be able to precisely know when you were working on something, as you might just be reading some documents.