Been a DisplayFusion user for many years. Due to the continuing plague of applications using Electron, I have a number of things I use that don't remember their window positions between launch and also constantly change the folders they are in based on updates (Teams and Discord among others). I've been using wildcards in my triggers and window position profiles to solve this. Here's examples of the process strings I use for each:
The problem I'm having is they just don't always seem to work. Sometimes the applications will have their triggers processed when they launch and sometimes they won't. This can be because when I restart my machine, they sometimes launch before DisplayFusion itself does but even manually triggering the window position profile in those cases doesn't always seem to work.
From what I've read in both the documentation and other threads here, I think I'm using the wildcards correctly, also evidenced by the fact that they do seem to work sometimes. I'm a bit baffled so I was wondering if anyone here could sanity check this for me.
Those trigger paths do look correct, you could even try something like:
*\Discord.exe
Can you give the simpler one a try and see if that makes any difference? Thanks!
Yeah it's weird, even when using *\, it doesn't seem to always be working. Teams is the main offender (as it always is) but it's happened with other applications as well.
I have a Once Per Process ID setup for Teams to move its window to a certain position at launch because it never remembers its last one. Looks like the attached but it's still launching in its default size.
I also updated an app I have called Android Messages this morning that is setup in a similar way and when it launched, it didn't snap to the right position either.
Could it matter that when DF doesn't relocate them, that I use Windows 11 Zones to position them instead? What I've done is use Zones to set the windows the way I want, then use the target function in the trigger to pull the display and window position based on that.
There are a couple of things that might affect this. The first is that DisplayFusion needs to be fully started or else it won't see the other applications start. The second is timing. Can you try adding a "wait" step before the move/maximize? Maybe a wait of 1000ms just to see if it is a timing thing where the window isn't done being created yet.
