I think I found a part of my display issues with Windows when running DF with triggers. The scripted functions I have that move windows to be inside monitor bounds (and not beneath the top taskbar) and also (now) handle moving windows to the mouse monitor without moving windows further away from the mouse are moving parts of windows.

The issue seems to be the Focus Event Trigger is called with the wrong window handle, e.g. not the top level window handle that gets focus, but rather a child window handle. For example, when File Explorer opens and displays the computer contents on the right pane, if I change focus to another window and back to File Explorer, I appear to get the right pane's window handle and not the top level File Explorer window handle.

I added a sound alert to my triggers when it doesn't get a top level handle, and so far I haven't heard a peep!

I just noticed the Create Window trigger doesn't seem to fire when I open an Outlook 2016 email message. I don't see anything unusual about the email window, it is a child of the desktop, but the trigger isn't firing?

Never mind, I think I just figured out the issue was Windows was running out of GDI objects as DF was over 8,000.

Seems like Outlook email windows not being triggered is happening at lower GDI levels occasionally - around 4,000.

Also, when I use Windows-L to lock, I normally get a trigger for the lockscreen image, but I saw it miss one today. I guess that could also be due to GDI handles?

I notice 8.0 beta 7 still doesn't consistently trigger on Outlook 2016 window creation as I am now using triggers again.

Perhaps DF could catch the window destroy message and remove window handles? Or, does Outlook not actually destroy the window, just hide it and then rebuild it?