https://www.displayfusion.com/Discussions/RSS/?TopicID=b3e14d10-540f-4f96-9332-a2cd790e5931 DisplayFusion RSS: BFS.Monitior.GetMonitorWorkAreas not working Sun, 19 Apr 2026 15:05:33 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=b3e14d10-540f-4f96-9332-a2cd790e5931 https://www.displayfusion.com/Discussions/View/bfsmonitiorgetmonitorworkareas-not-working/?ID=b3e14d10-540f-4f96-9332-a2cd790e5931#2 Thu, 02 Apr 2020 20:14:31 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/bfsmonitiorgetmonitorworkareas-not-working/?ID=b3e14d10-540f-4f96-9332-a2cd790e5931#2 DisplayFusion We actually just fixed this up internally yesterday, so it'll be good to go in the next beta

Thanks! ]]> https://www.displayfusion.com/Discussions/View/bfsmonitiorgetmonitorworkareas-not-working/?ID=b3e14d10-540f-4f96-9332-a2cd790e5931 Thu, 02 Apr 2020 20:02:16 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/bfsmonitiorgetmonitorworkareas-not-working/?ID=b3e14d10-540f-4f96-9332-a2cd790e5931 DisplayFusion I have a script that uses GetMonitorWorkAreas and it is returning a 0 length array for my two monitors. GetMonitorWorkAreaByWindow seems to work for one monitor. My monitors are identical, with monitor 2 on the left, monitor 1 on the right.

I am running Windows 10 Version 1809 (Build 17763.109
I am running DisplayFusion Pro 9.7 (Beta 6).
I am running nVidia Graphics Driver 442.74.

Any ideas of what might be happening?

PS I have worked around it for now using GetMonitorIDs and looping through GetMonitorWorkAreaByID. ]]>