DisplayFusion RSS: Timer interval trigger fires too soon after unlock

DisplayFusion RSS: Timer interval trigger fires too soon after unlock https://www.displayfusion.com/Discussions/RSS/?TopicID=47f5711c-dde6-44ec-90b4-18e465255bb1 DisplayFusion RSS: Timer interval trigger fires too soon after unlock Sun, 19 Apr 2026 15:06:48 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=47f5711c-dde6-44ec-90b4-18e465255bb1 RE: Timer interval trigger fires too soon after unlock https://www.displayfusion.com/Discussions/View/timer-interval-trigger-fires-too-soon-after-unlock/?ID=47f5711c-dde6-44ec-90b4-18e465255bb1#8 Sun, 22 Mar 2020 18:39:09 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/timer-interval-trigger-fires-too-soon-after-unlock/?ID=47f5711c-dde6-44ec-90b4-18e465255bb1#8 DisplayFusion I removed the wait from both restore triggers (desktop unlocked + monitor profile changed) and I'll keep you posted. ]]> RE: Timer interval trigger fires too soon after unlock https://www.displayfusion.com/Discussions/View/timer-interval-trigger-fires-too-soon-after-unlock/?ID=47f5711c-dde6-44ec-90b4-18e465255bb1#7 Fri, 20 Mar 2020 15:21:28 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/timer-interval-trigger-fires-too-soon-after-unlock/?ID=47f5711c-dde6-44ec-90b4-18e465255bb1#7 DisplayFusion Thanks! If you take the "Wait" action out of the restore Trigger rule, does that make any difference? Or does that break the restore? ]]> RE: Timer interval trigger fires too soon after unlock https://www.displayfusion.com/Discussions/View/timer-interval-trigger-fires-too-soon-after-unlock/?ID=47f5711c-dde6-44ec-90b4-18e465255bb1#6 Thu, 19 Mar 2020 21:49:09 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/timer-interval-trigger-fires-too-soon-after-unlock/?ID=47f5711c-dde6-44ec-90b4-18e465255bb1#6 DisplayFusion Thank you for the information! We're a bit backed-up right now but we'll take a look as soon as we can and get back to you. Thanks!

Open the Settings > Troubleshooting tab
Click the "Export Info to File" button
Reply with the file attached

]]> RE: Timer interval trigger fires too soon after unlock https://www.displayfusion.com/Discussions/View/timer-interval-trigger-fires-too-soon-after-unlock/?ID=47f5711c-dde6-44ec-90b4-18e465255bb1#3 Fri, 06 Mar 2020 18:50:09 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/timer-interval-trigger-fires-too-soon-after-unlock/?ID=47f5711c-dde6-44ec-90b4-18e465255bb1#3 DisplayFusion I have that setting enabled, and after doing a little more testing, it looks like the trigger is cancelled while locked and then starts again when unlocked - which is expected behavior.

Can the monitors going to sleep affect the save trigger behavior in any way? Or perhaps the restore?

I've attached my trigger configurations for save and restore. ]]> RE: Timer interval trigger fires too soon after unlock https://www.displayfusion.com/Discussions/View/timer-interval-trigger-fires-too-soon-after-unlock/?ID=47f5711c-dde6-44ec-90b4-18e465255bb1#2 Thu, 05 Mar 2020 20:39:42 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/timer-interval-trigger-fires-too-soon-after-unlock/?ID=47f5711c-dde6-44ec-90b4-18e465255bb1#2 DisplayFusion In 9.6.1 we added an option to Trigger edit window called "Don't run this trigger when the desktop is locked" that should help here. Can you try enabling that in your Trigger rules? ]]> Timer interval trigger fires too soon after unlock https://www.displayfusion.com/Discussions/View/timer-interval-trigger-fires-too-soon-after-unlock/?ID=47f5711c-dde6-44ec-90b4-18e465255bb1 Thu, 05 Mar 2020 03:23:33 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/timer-interval-trigger-fires-too-soon-after-unlock/?ID=47f5711c-dde6-44ec-90b4-18e465255bb1 DisplayFusion Hi, I'm using DisplayFusion mainly to restore window positions when unlocking using the instructions from https://www.displayfusion.com/Discussions/View/automatically-saving-and-restoring-window-positions-on-dockundock. It usually works however I noticed that it can result in windows not being restored due to the trigger executing immediately after the unlock. Consider the following scenario:

- 30 second timer interval trigger is setup to save window positions
- trigger executes at 12:00:00 and saves window positions, next trigger is scheduled to run at 12:00:30
- lock at 12:00:15
- unlock at 12:00:29
- trigger executes at 12:00:30 before the windows get a chance to be restored, saving the wrong positions

One naive solution would be to pause the timer when locked and unpause the timer when unlocked. However this can also fail when locking right before the timer executes - in the scenario above if I locked at 12:00:29 and unlocked at 12:00:40 the trigger would execute at 12:00:41 which will still not be enough time for the restore to happen (the frequency and probability of this failure depends on the interval duration).

Another solution would be to use a priority queue when executing triggers and run the timer interval trigger with lowest priority - this would ensure the restore trigger is executed before the timer interval.

Yet another solution would be to cancel any active timers when locked and restart them when unlocked.

Is there any fix for this issue in v9.6.1? ]]>