Hi there,

I installed the v9.0 update today (was on v8.0), and have noticed my Monitor Profile / Trigger / Functions have stopped working as expected.

I have two monitor profiles, A and B. Profile A has Monitor 1 on the left, Monitor 2 on the right.
Profile B reverses this.

I then have two functions that move a couple of applications onto a specific monitor per profile:
If Profile A, apps move onto Monitor 2
If Profile B, apps move onto Monitor 1
I use a trigger to fire these functions which looks for monitor profile changing.

As of v9.0, when I change monitor profile, the function does not fire. If I run the function manually from the editor, it fires as expected and moves application windows around as required.

My question is, is this a potential bug, or has the functionality around triggers/functions changed for v9.0?

Thanks!

It does indeed. Everything looks like it's working, just the function never seems to get triggered.

Hope this helps!
Note: the DebugInfo.html I had appears to have been unchanged since 2015 (last time I ran it through Steam perhaps?) but there is a DebugInfoNormal.html which is up to date.

In DisplayFusion.log, lines 1304 and 1516 look to be where I switch profiles. I switch to 'Work' profile, and then back to 'Normal'.

If it helps, the functions I call are apps.Work and apps.Normal, using 'Monitor Profile Changed' triggers. Two apps that should be responding to the functions are mIRC and Steam (Friends view)

Also, I've got two triggers listening on Window Focused to handle moving any Teamspeak windows around, as for whatever reason Teamspeak didn't play nice with BFS.Window.SetSizeAndLocation back when I scripted the functions, so I just have the trigger move that between monitors depending on monitor profile in use - this still works fine (the trigger looks for either ts3client_win64.exe or window class: Qt5QWindowIcon)

Sorry for the delay!
Here's the logs from Log Detailed, lines 864 and 1191 are when I switch profiles (on line 807, I hit the shortcut for the current profile by mistake)

Oh interesting. I rebooted this morning as I noticed Windows wasn't automatically sleeping the screen after being inactivate for an hour.

The triggers/functions are now working just fine! I don't know if this is related to updating the GPU drivers a couple of days ago, maybe something got stuck somewhere and a reboot sorted it out.

Sorry to bother you with this! Looks like it was just a small fault that a reboot fixed.