[Issue solved] "Window Destroyed" trigger

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

eklundchristopher

2 discussion posts

I'm experiencing issues where the "Window Destroyed" trigger isn't executed for certain programs/games. More specifically, FIFA 16 and DayZ. My initial thought would be that Steam and Origin manipulate the process in some way when they shut it down and it therefore isn't registered as it should, but then again, FIFA 17 through Origin works flawlessly... Tried hooking into the process, the window title, the window class etc to no avail.

Has anyone experienced similar issues and found a workaround? or is this a known bug?

PS. I'm using the 8.1 beta 2 version (tried the latest stable version first) and Windows 10.

Thank you!

Oct 23, 2016 (modified Oct 23, 2016) • #1

eklundchristopher

2 discussion posts

I solved it by creating a scripted function, which I then registered in the Window Created trigger for my applications. If anyone else is having similar issues, this is the piece of code I used for the scripted function:

Code
Copy
Select All

using System;
using System.Drawing;

public static class DisplayFusionFunction
{
    public static void Run(IntPtr windowHandle)
    {
        const int waitForever = 0;

        string appPath = "C:\\Program Files (x86)\\Steam\\steamapps\\common\\DayZ\\DayZ.exe";

        uint appId = BFS.Application.GetAppIDByFile(appPath);
        BFS.Application.WaitForExitByAppID(appId, waitForever);
        
        BFS.DisplayFusion.LoadMonitorProfile("Default");
        // Do your own stuff here...
    }
}

You'll obviously have to substitute the appPath & monitor profile name (or do whatever else you need it to do) with your own.

Oct 23, 2016 (modified Oct 23, 2016) • #2