Papa Quebec70505
17 discussion posts
Hi,
I have several triggers set to move windows when created. After coming back from a lengthy break from pc usage, many of the triggers don't work anymore.
Windows 10. Triggers are "window text" recognition with delay before checking match conditions.
Where should I begin troubleshooting here? I have a firefox window trigger that works, another application that works as well, but for example the confirmation window "do you want to keep changes" after switching displayfusion profiles, won't move to the selected window...
Can you send me a screenshot of one of the triggers that isn't working?
Thanks for sending that over. A few things to check here:
1. Make sure the "Delay before checking match conditions" value is set to at least 2000ms. The Window Text is usually the last thing to get set on the window, so sometimes DisplayFusion fires before it's set and it gets missed.
2. Is the Window Text changing from the time you save it to the time it loads? The first screenshot has the version number in the text, so when the app updates it will probably break. The Window Text is a CONTAINS match though, so you can cut out the version number and it will still match.
3. For the triggers that have the "Monitor Profile" match condition enabled, if you open the Monitor Configuration window, does it show the correct profile is detected in the upper left corner?
Papa Quebec70505
17 discussion posts
Ok, I'm getting somewhere. Indeed for profiles 3 and 4, the issue was that even though I loaded the monitor profile through a shortcut, the monitor configuration window did not recognize the profiles anymore. So I saved them again, now the top left corner shows the profile, and these two triggers work again.
For the Air `Manager profile, there seem to be several problems - one is that I have another trigger for another window that also contains the word "Manager", and therefore triggered the wrong action. I removed the ambiguous word, but I still can't get it to do what I want, i.E. move it and minimize it...
Papa Quebec70505
17 discussion posts
Ok, everything is solved now.
The problem was a combination of issues, which got me so confused. First the monitor profile not being recognized, despite it just having been loaded, thats kinda odd, but fixed now by simply saving after loading. Then the multiple windows with similar wording. And now lastly, I just found out that delay before checking match conditions is not the same as the wait action.
I was now finally able to configure everything the way I need it to. Thank you for your input, that was the decisive hint to getting me to figure it out.
