So after just finishing my Windows 10 upgrade to 1809, I'm noticing now that when I click the clock on my secondary monitor it opens up on my primary monitor then teleports over to my secondary.
I think this "bug" is new and didn't happen in 1803, hope you can reproduce it and fix it eventually, it's driving me crazy. If you need any more info let me know.
I believe that's always been the case, but it's a timing thing as to whether or not you see it open on the first screen. Depends on how quickly the polling picks it up because we can't hook it
On my machine with 1809, about half the time I don't see it on the primary monitor first and the other half it shows up for a second before it gets moved.
How long is it before it gets moved on your machine, and is it consistent?
But it did get fixed! The only thing that changed recently was the 1809 update, and that's when I noticed, so I'm blaming that, I've also been rocking 9.4 Beta 3 for a week or so while on 1803 before the update happened, and never had issues with the clock.
That's always been the case, but Windows 10 Start Menu is total garbage and has been replaced by Classic Shell (now Open-Shell) from pretty much day one, so who cares about that.
That's always been the case, but Windows 10 Start Menu is total garbage and has been replaced by Classic Shell (now Open-Shell) from pretty much day one, so who cares about that.
Classic shell doesn't have this issue? I might have to switch.
I've just confirmed with our devs that in Windows 10, we've always had to open the Clock/Calendar popup on the main screen first, then poll for the window and move it, so it's definitely just a timing thing as to whether you see it open on the primary first or not.
