In the latest beta versions (I had to revert to 11.0.5 to get back the original functionality) when I open a new application that has many dependent windows that open with it (in my case 50 different windows/charts), they all open on the active monitor where the mouse is. This is wrong and unwelcome.
Before it was a great function, I could click on the app icon on the taskbar of the monitor where I wanted to open an app and it was opening on the active monitor, but now I have to deactivate the function or revert back to 11.0.5 which functions correctly. When an app has stored the location of the many previously opened windows, the dependencies should not open all on the active monitor, it is a mess, only the window that we just launched.
Also, the latest betas were messy, the monitor config was messy and corrected soon after etc. But for now, I will stay at the older version for the above-mentioned reason.

Has anybody from Binary Fortress taken this into account yet? Not a serious enough bug?

Well, it was working correctly like I described since 2018!!!! So forgive me if I insist that the recent modification is the bug. You cannot override like this the memory of the all the other windows saved-stored. Only the first window of the app makes sense to launch at the active monitor. I will have to de-activate this function then whereas I want it for all new apps, except the ones with multiple windows.
Moreover I did not see this change documented in any of the changes in the newer releases.

If you're looking for it to just move a specific window, you can have more granualar control with triggers, we have a guide on creating them here: https://www.displayfusion.com/HelpGuide/Triggers/

Thanks![/QUOTE]

If you're looking for it to just move a specific window, you can have more granualar control with triggers, we have a guide on creating them here: https://www.displayfusion.com/HelpGuide/Triggers/

I tried to reproduce this functionnality with a trigger (Window Created-Process Filename *.* for all processes, Action: move to mouse cursor monitor) but it does not work. Could you help me?
Thank you.

Thanks![/QUOTE]

I had to write triggers for every app that I use frequently to replace this change in functionnality, but I found it works. Still I find strange to claim that something that worked in one way for 5 years now is supposed to work differently