On Tue, Jul 7, 2020 at 12:18 PM David Edmundson <da...@davidedmundson.co.uk> wrote:
> >It seems that the most popular Wayland protocol for detecting when a > user is "idle" is this protocol that is a part of KDE. > > Yes-ish. > > Note it is now being upstreamed: > > https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/29 > > So now is a good time for any changes. > > Any discussion should happen there. I have a feeling you're effectively > responding to the question Simon had about interaction with idle-inhibit > and whether we really want to inhibit idle events or actions on idle events. > > >One limitation that I have with this protocol is that if the user stops > typing/mousing, but is watching a video or something, the video player > can send fake activity with the `simulate_user_activity` request. > > That's not really right. > One should use an idle inhibition protocol. Annoyingly this is fragmented, > there's one in x and wayland but also some DBus ones. > `simulate_user_activity`will get deprecated at some point, it just exists > from a time to fake things in X and us mapping it. > > >My application is trying to track actual keyboard/mouse activity, and > this fake activity makes things difficult (even though it is an > effective way to prevent a lockscreen from triggering). > > I suspect it's idle inhibitions that's breaking it, not this simulate user > activity. Let's follow this up on the relevant wayland-protocols thread > above > > David > > Relevant comment: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/29#note_560996
