Notice: This forum has been recovered from an old backup, so some content, links, and dates may be outdated. The forum is currently read-only while we restore sign-in and registration functionality. Details
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
System.Idle doesn't work very well
System.Idle doesn't work very well
I'm running EG 0.4.1.r1710 on Windows 10 Enterprise and I'm looking to trigger actions when my system has been idle for a set amount of time. I see the System.Idle event fire when I haven't moved the mouse, clicked a mouse button, or pressed a key in the Idle timeout. Unfortunately, this fails in a bunch of different edge cases. If I'm reading a long text and scrolling with the mousewheel? That's not picked up, and Idle will trigger while I'm actively using the system. If I'm in an RDP session and actively typing and clicking? That isn't detected either, and EG will happily trigger the Idle event while you're in the middle of using the system. Is there some way to catch actual, physical system interaction and reset the idle time appropriately? Whatever the current version of EG is looking at to determine system idle time doesn't appear to be very robust.