I use DisplayFusion 9.4 beta 2 (Steam) on Windows 10 and have a minor issue with Spotify (exe, not UWP).
When my system starts Spotify is set to automatically launch, but when it does the main window appears on my left-most monitor but its titlebar buttons (pin, minimize, maximize, close) are not drawn on the window but instead appear on my centre (main/taskbar) monitor.
Once I interact with any of these buttons they jump to the Spotify window and there is no more issue. I also cannot reproduce the issue if I close Spotify and launch it in the same Windows session.
If you disable the "Start with Windows" option in DisplayFusion, then restart, does the same issue happen with the Spotify window?
Edit: I misread your original post, just realized you're talking about the TitleBar Buttons, not the caption buttons. I'll test this out here and see what I can find out.
Thanks!
Sep 17, 2018 (modified Sep 17, 2018)
•
#2
I couldn't reproduce this here with default settings. Could you attach a backup of your DisplayFusion Settings so that I can test with them? (Settings > Options > Export)
Thanks!
Here it is.
• Attachment [protected]: DisplayFusion Backup (2018-09-18 @ 20-01, 9.3.99.102, HYDRA).reg [158,134 bytes]
File attached!
• Attachment [protected]: DisplayFusionDebugInfo.zip [26,631 bytes]
Thanks! I still can't seem to reproduce this issue here. Could you attach a screenshot of what it looks like when it's broken?
This is what I am seeing. The moment I use minimize/maximize or move the Spotify window, everything snaps into place.
•
Attachment: sfy.JPG [82,942 bytes]
sfy.JPG
Here's the log. Spotify opened at 16:48, almost on the dot (no more than 6 or 7 seconds into the minute).
The moment the Spotify window is being drawn, I already see the titlebar buttons on the other (wrong) monitor, I don't see them jump or anything like that.
/Edit: the Spotify window has the class Chrome_WidgetWin_0.
• Attachment [protected]: DisplayFusionDebugInfo.zip [85,609 bytes]
Sep 25, 2018 (modified Sep 25, 2018)
•
#11
Thanks, yeah I don't see anything in the log indicating that DisplayFusion is moving the window, so that's good at least. And to 100% confirm, if DisplayFusion doesn't run at startup, this issue doesn't occur?
What if you disable DisplayFusion from startup, wait for Spotify to open, then launch DisplayFusion manually?
I tried disabling DF on startup last week, but I tested again today just to be sure.
DF has updated to 9.4 beta 3 without any change in behaviour.
If DisplayFusion is not started at launch but Spotify is, Windows opens with Spotify behaving normally (all buttons on the titlebar, attached to the window). Nothing changes to the Spotify window when I then start DF except that the extra titlebar buttons are added.
If Spotify is not started at launch but DF is, when I open Spotify after logging into Windows it behaves normally.
It's only when both are set to launch with Windows that I get this odd behaviour.
Wow, I'm really stumped here! If you disable some DisplayFusion features, like TitleBar Buttons and Triggers, does that make any difference?
Disabling triggers has no effect, but it does not happen if I disable Titlebar buttons!
Wow, interesting! How about if you re-enable the TitleBar Buttons after Spotify has already launched?
I did a couple of restarts to be sure only the Enable Titlebar Buttons option has any effect on startup and it's definitely the case that if that option is enabled AND both DF and Spotify launch with windows, the weird positioning happens.
If I enable the titlebar buttons after Spotify has already launched nothing weird happens, everything remains in place.
Very interesting. It seems like some kind of weird race condition. I will put a ticket on our list to delay loading of titlebar buttons on the Spotify window a bit to see if that helps. I'll keep you posted when we have a beta available with that change made.
