Trigger stopped working

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

Mrrellim69

16 discussion posts

I have six triggers set up but all of a sudden one of them stopped working even though it is very similar to another one that still works.

That attached image "Activity list DF" is the one that stopped working, and "Calendar DF" still works and other than the window text they are identical in that the trigger is event is a window being created and they have the same action.

There have been no updates to the program that these windows are from.

I have over ever change my system from a desktop to a laptop, so I now have 4 montiors (laptop as 1, and then 3 external monitors) versus 2 monitors.

Oct 26, 2023 • #1

It doesn't look like the image got attached, could you attach it again?

Oct 27, 2023 • #2

Mrrellim69

16 discussion posts

Hopefully it works this time.

• Attachment [protected]: Pictures.7z [102,096 bytes]

Oct 27, 2023 • #3

Thanks for sending that over. The version might have changed in the window text, if you change it to just read "Activity List", does that work?

You can also try adding a 1000ms "Delay before checking match condition" to see if that helps.

Oct 27, 2023 • #4

Mrrellim69

16 discussion posts

The version number is still the same in the window text. I have added the delay but that does not make a difference.

Oct 28, 2023 • #5

Could you do the following to send me some more information from the Activity List window?

Install one of our other apps, Window Inspector: https://www.binaryfortress.com/windowinspector (it's free)
Open the Activity List window
Open Window Inspector
Hover over the affected window with your mouse so that the affected window's info shows in the Window Inspector window
Press Ctrl + Shift + F1 to freeze the timer in Window Inspector
Press Ctrl + Shift + F2 to save the info from Window Inspector to a file
Send me the file from the previous step

Thanks!

Oct 30, 2023 • #6

Mrrellim69

16 discussion posts

I think I did it correctly!!

Thanks

• Attachment [protected]: OfficeTools WorkSpace - Activity List - OfficeTools_ version 3.10.77 (Oct 30, 2023 @ 14_09).html [74,783 bytes]

Oct 30, 2023 • #7

Thanks! Could you try changing the Window Text field in the Trigger rule to just "Activity List"? I'm wondering if the hyphen is being treated as a "NOT" and causing some issues there.

Oct 30, 2023 • #8

Mrrellim69

16 discussion posts

I tried that and it didn't work. Also tried just "Activity" and that didn't work either.

Just a reminder that the trigger for the Calendar has the hyphen in the window name.

Oct 30, 2023 • #9

That's really strange! Could you send over a debug log?

On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
Open the Activity List window and note the time so we'll know where to check in the log file
Open the Calendar window and note the time
Click the "Export Info to File" button on the Settings > Troubleshooting tab
Reply with the file attached
Disable debug logging after sending the log

Thanks!

Oct 31, 2023 • #10

Mrrellim69

16 discussion posts

Calendar window opened at 1:22 and the trigger worked sucessfully.

Activity window opened at 1:23 and the trigger did not work.

• Attachment [protected]: DisplayFusionDebugInfo.zip [95,305 bytes]

Oct 31, 2023 • #11

Thanks! I'm not seeing any log lines that would indicate that the Activity List window is a newly created window, which would be why the DisplayFusion Trigger rule isn't detecting it. Could you try changing the Trigger Event in the rule for the Activity List window to "Window Focused"?

Nov 1, 2023 • #12

Mrrellim69

16 discussion posts

Using "Window Focused" appears to have worked.

Thanks

Nov 6, 2023 • #13