Hollo
167 discussion posts
Since Beta20 (possibly Beta19, I was unable to use that version because it broke an essential funcionality for me), the Windows calendar always opens on the primary monitor instead of the one the systray clock was clicked on.
Currently using Beta21 and the problem is still present.
Thanks for the heads up on this! I was able to reproduce this here as well and have added it to our list to fix up for the next beta.
Hollo
167 discussion posts
Now it opens on the primary monitor first and then jumps to the current one after a ~0.5s delay.
It's definitely better but wasn't delayed in earlier DF versions.
Is there a setting or something to fix this?
Hollo
167 discussion posts
I took this for another issue a few days ago but haven't changed anything since then, hope it will suffice.
Please tell me if this is not good and then I'll make another one.
• Attachment [protected]: DisplayFusionDebugInfo_20230301.zip [49,404 bytes]
Thanks! I've tested in Windows 10 with your monitor setup, on DisplayFusion 9.9 and 10.0 Beta 22, and the both behave the same way. The Calendar opens on the primary first, then moves, which is expected. We have to poll while we wait for it to open and then move it once it's visible.
Were you comparing to 9.9 or an even earlier version?
Hollo
167 discussion posts
That is strange, I was using pretty much every beta version for years (so, comparing to 10.x) and I've never noticed this, so maybe the delay was always there, just not that much?
It's definitely always been there, and we haven't intentionally increased it. When I test here it's the same for 9.9 and 10.0 B22.
Hollo
167 discussion posts
Alright then I guess this is as good as it gets.
Thanks!
