"User-Inactivity" Timeout configurable

DanielSchreiber

For me it happens quite often, during Teams calls that Workinghours stops the timer due to being "inactive" (probably I didn't touch the mouse/keyboard for some minutes). This is annoying and incorrect - probably for most users.

Possible solutions:

Only trigger "inacitivity" when OS is locked and/or screensaver is on (preferred)
Configurable timeout for inactivity

P.S.: I'd buy the Pro-Version for this feature 😃

WorkingHours version:
OS + version: Win 10, v2.9.13.0

timo

Unfortunately, there is no API to configure that. It's determined by Windows alone.

DanielSchreiber

Could this be used: https://stackoverflow.com/a/770165/2544163 ?

timo

No, I don't think so. WorkingHours is a UWP app which has limited access to Windows APIs.

DanielSchreiber

Ok, but a configurable delay that is added to the currently implemented inactive triggers should be possible?

timo

Never thought of that. Would probably be possible, but feels a bit too hacky to me.
How would you label such a setting? "Additional delay to the idle time which is determined by Windows"?

DanielSchreiber

To me, the default windows idle timer feels hacky 😃 (didn't really find docs on when exactly this is triggered..)

Maybe something like "idle time grace period" would make sense?

Or to be more specific - I'd add a 4th option "Time pausieren nach.." (Pause timer after..) and when this is selected a number input to the right is shown with label "Minuten" (Minutes)

timo

Yes, the idle time is undocumented and can vary from user to user / PC to PC.
An input field wouldn't make sense, as the app doesn't know how long the inactivity has been before the inactivity event is being sent.
As Microsoft currently seems to transition from the UWP framework to the WinUI framework that offers developers more access to OS features, I might just wait another year or so and then migrate to WinUI. Maybe this will give me access to APIs that make it possible to properly implement a better, configurable idle detection. Calling Win32 API seems to be possible with WinUI: https://learn.microsoft.com/en-us/windows/apps/winui/winui3/desktop-winui3-app-with-basic-interop

DanielSchreiber

ok - but exactly because the app does not know about the timing would be a reason to make this configurable, because the user does have an impression, if the idle triggers to early?

Anyways, I'll try to stop nitpicking - it still is a nice app 🙂