DisplayFusion RSS: Broken Triggers in v11 Beta 4 https://www.displayfusion.com/Discussions/RSS/?TopicID=018f108d-f522-75aa-b855-7eb61060f8bc DisplayFusion RSS: Broken Triggers in v11 Beta 4 Thu, 16 Apr 2026 18:40:02 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=018f108d-f522-75aa-b855-7eb61060f8bc RE: Broken Triggers in v11 Beta 4 https://www.displayfusion.com/Discussions/View/broken-triggers-in-v11-beta-4/?ID=018f108d-f522-75aa-b855-7eb61060f8bc#8 Wed, 26 Jun 2024 14:42:18 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/broken-triggers-in-v11-beta-4/?ID=018f108d-f522-75aa-b855-7eb61060f8bc#8 DisplayFusion It takes a few seconds, but it seems to work after a quick test.

Must better than 1+ minutes anyway. :P ]]> RE: Broken Triggers in v11 Beta 4 https://www.displayfusion.com/Discussions/View/broken-triggers-in-v11-beta-4/?ID=018f108d-f522-75aa-b855-7eb61060f8bc#7 Wed, 26 Jun 2024 14:34:02 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/broken-triggers-in-v11-beta-4/?ID=018f108d-f522-75aa-b855-7eb61060f8bc#7 DisplayFusion Downloading it now. I'll let you know.;) ]]> RE: Broken Triggers in v11 Beta 4 https://www.displayfusion.com/Discussions/View/broken-triggers-in-v11-beta-4/?ID=018f108d-f522-75aa-b855-7eb61060f8bc#6 Wed, 26 Jun 2024 13:51:27 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/broken-triggers-in-v11-beta-4/?ID=018f108d-f522-75aa-b855-7eb61060f8bc#6 DisplayFusion We've released a new beta that should fix this up, please let me know if you run into any issues after updating. ]]> RE: Broken Triggers in v11 Beta 4 https://www.displayfusion.com/Discussions/View/broken-triggers-in-v11-beta-4/?ID=018f108d-f522-75aa-b855-7eb61060f8bc#5 Fri, 26 Apr 2024 15:05:25 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/broken-triggers-in-v11-beta-4/?ID=018f108d-f522-75aa-b855-7eb61060f8bc#5 DisplayFusion Okay interesting, we'll add it to our list and see what we can find there ]]> RE: Broken Triggers in v11 Beta 4 https://www.displayfusion.com/Discussions/View/broken-triggers-in-v11-beta-4/?ID=018f108d-f522-75aa-b855-7eb61060f8bc#4 Thu, 25 Apr 2024 14:40:02 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/broken-triggers-in-v11-beta-4/?ID=018f108d-f522-75aa-b855-7eb61060f8bc#4 DisplayFusion @Owen: Yes, it works just fine with v10.1.2.

EDIT: In case it makes a difference, I'm using Windows 10.

Code
Copy
Select All

C:\WINDOWS\system32>wmic os get version
Version
10.0.19045
]]> RE: Broken Triggers in v11 Beta 4 https://www.displayfusion.com/Discussions/View/broken-triggers-in-v11-beta-4/?ID=018f108d-f522-75aa-b855-7eb61060f8bc#3 Thu, 25 Apr 2024 14:38:28 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/broken-triggers-in-v11-beta-4/?ID=018f108d-f522-75aa-b855-7eb61060f8bc#3 DisplayFusion Yeah it doesn't look like that app has a normal startup process using a Window Created event we can fire off. It works fine if you roll back to 10.1.2? ]]> RE: Broken Triggers in v11 Beta 4 https://www.displayfusion.com/Discussions/View/broken-triggers-in-v11-beta-4/?ID=018f108d-f522-75aa-b855-7eb61060f8bc#2 Wed, 24 Apr 2024 14:50:50 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/broken-triggers-in-v11-beta-4/?ID=018f108d-f522-75aa-b855-7eb61060f8bc#2 DisplayFusion In case you've already read the discussion, I edited the first post and added some observation and further info at the bottom of it. ]]> Broken Triggers in v11 Beta 4 https://www.displayfusion.com/Discussions/View/broken-triggers-in-v11-beta-4/?ID=018f108d-f522-75aa-b855-7eb61060f8bc Wed, 24 Apr 2024 14:41:30 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/broken-triggers-in-v11-beta-4/?ID=018f108d-f522-75aa-b855-7eb61060f8bc DisplayFusion I actually noticed this issue with Beta 3 (upgrading straight from v10.1.2) but I forgot to report it.

===

I have a trigger to move an application to a specific screen that doesn't work. Here's how I setup the filter:

TRIGGER BOX
    Trigger Enabled (obviously :D)
    Event: Window Created
    Frequency: Always
    Stop processing triggers if this one matches: Enabled (I tried also disabling it, but nothing changed)

MATCH CONDITIONS BOX
    Process Filename: The app's executable "fmd.exe" (see download link below)
    Delay before checking match conditions (MS): 0

ACTIONS BOX
    Move Window to Selected Monitor: #2
    Maximize Window: -

====

The app's window remains where it opens (on monitor #1). Even the DF taskbar's option (on monitor #2) with the enabled option Force application to start on the same monitor as Taskbar has never worked with it (which is why I added the trigger).

The application is the same one I mentioned in this previous discussion: https://www.displayfusion.com/Discussions/View/displayfusion-101-beta-3-now-available/?ID=ec71555f-4c81-4c07-a52b-ac46b0b6ab50#8

The version currently being used is the latest one: fmd_2.0.32.0_x86_64-win64.7z

===

One thing I noticed, is that with Beta 3 the window was still moved to monitor #2 after 40-50 seconds. However, with Beta 4 the window is moved even later (right now in my last test it took 4+ minutes).

Also, I have to manually move it by clicking the application's titlebar and manually drag it to monitor #2. Neither the shortcut registered to move the window to the next monitor (CTRL+WIN+X) nor the titlebar's button "Move Window to Next Monitor" work. ]]>