DisplayFusion RSS: Window Destroyed

RE: Window Destroyed

Binary Fortress Software — Mon, 08 Jan 2024 15:51:16 GMT

@JLJTGR Thanks for helping out!

RE: Window Destroyed

Binary Fortress Software — Sat, 06 Jan 2024 12:01:34 GMT

I tested this today and found there is a very quick flash of a splashscreen at startup, barely noticable. The splash seems like a nanosecond.

I was curious so I took a video of the screen using SnagIt & replayed until I found the few frames that had the splash. There were actually two quick splash screens, one with the auto-filled login info. I changed the trigger to use Window Class instead. Oddly, the identifier, "Qt5QWindowIcon", has no resemblance to the program name...

99.5% of my programs do not have splash screens. I just happened to choose one that did to try .Destroy for the first time. Good lesson learned. 🖖

😍 DisplayFusion

RE: Window Destroyed

Binary Fortress Software — Sat, 06 Jan 2024 06:31:16 GMT

If the program has something like a splashscreen at startup, that would be a window and it might destroy it soon after. But there could be other things that qualify that aren't even visible. It's hard to say.

If you're looking for the program closing and you already know what the main window is, just drag the crosshair from Window Class to the program and filter it to that.

Window Destroyed

Binary Fortress Software — Fri, 05 Jan 2024 21:29:37 GMT

I currently have a trigger that fires on a particular program startup, which works fine. I would now like to add a 'shutown' trigger for that same program.

To accomplish this, I created a Window Destroyed trigger (A) which calls a sub-function (B). It does fire when the program is closed, but it seems to also fire when the program is started. I verified my suspicion by adding a 'Show Notification' action.

Is this the correct event to choose (C) to fire a fuction on a program close?