[BUG] Third Monitor Lost Time.

[ZeroPoke]

When I installed this on Launch day of Windows 11, I have time on all three monitors.
Now I only have time on monitor 1 and 2.

To Reproduce
No idea. I just noticed it when I got up this morning. and it was still gone after a reboot.

Expected behavior
Time on all three monitors.

Screenshots
https://i.pl0x.in/1e3a4a034ab2948607e2c837/bfdff7be.png

[marticliment]

Check release 1.9 and install the version with the alignment fix.
Then follow the instructions in the last comment on issue #40

[ZeroPoke]

It does not fix the issue. The clock flashes there for a second and disappears again. Quit and open it again and its not there. Tried this a couple times just to make sure.

[GoLLuM-G13]

Hi,
Tried both 1.9 and 1.9 with alignment fix and had the same issue with the third screen

[csongorBertalan]

Hi I've been using it on win 11 since August with no problem.
CPU: i7-8750H
Brand: Dell G3

I just upgraded windows on my second laptop and I can see it on all 3 monitors.
CPU: i5-8365U
Brand: Dell Latitude 5040

[marticliment]

Yes, this is a bug that affects only some users, i'm trying to figure out what is happening...

[GoLLuM-G13]

If it is of any help, I tried the 1.8 version, and it worked perfectly until the auto-update installed the 1.9

And I think I found out why I have this issue, my monitors' setup is like this from left to right "Monitor 1" - "Monitor 3" - "Monitor 2", "Monitor 3" being the main screen.
When I use the 1.9 version, it adds a clock on the left one "Monitor 1" but not the right one "Monitor 2". But when for a test I made the left one "Monitor 1" as my main monitor, it showed the clock on both of the two other monitors.
If I make "Monitor 2" my main monitor, I have the same result as the first scenario, it adds the clock on a single monitor only "Monitor 3".
So my guess is that the app follows the monitor's "identity number", it will add a clock on all the numbers above the main one, if it's 1, no problem (this is what we see with laptops mostly, as with the two scenarios of @csongorBertalan)
The "exception" is when the third monitor (on three) is the main screen, there isn't a number above it, so it adds a clock on the first monitor only.

I really hope that can help for what's next.

Good luck

[csongorBertalan]

Hi there,

Good idea. I tested it.
No matter which monitor I set s the main Monitor, it still shows up on all three.

[urifoox]

I don't think that's true - my main monitor is 6 works fine on mine.

[marticliment]

If it is of any help, I tried the 1.8 version, and it worked perfectly until the auto-update installed the 1.9

And I think I found out why I have this issue, my monitors' setup is like this from left to right "Monitor 1" - "Monitor 3" - "Monitor 2", "Monitor 3" being the main screen. When I use the 1.9 version, it adds a clock on the left one "Monitor 1" but not the right one "Monitor 2". But when for a test I made the left one "Monitor 1" as my main monitor, it showed the clock on both of the two other monitors. If I make "Monitor 2" my main monitor, I have the same result as the first scenario, it adds the clock on a single monitor only "Monitor 3". So my guess is that the app follows the monitor's "identity number", it will add a clock on all the numbers above the main one, if it's 1, no problem (this is what we see with laptops mostly, as with the two scenarios of @csongorBertalan) The "exception" is when the third monitor (on three) is the main screen, there isn't a number above it, so it adds a clock on the first monitor only.

I really hope that can help for what's next.

Good luck

Well, the thing is more or less like this, but it's not because of elevenclock but because of Qt or by Windows. The program analyses all screens, identifies the first one and skips it, but the other ones will show a clock. The reason it worked before and not it does not is weird, because I've not changed this part of the code (and for me it still works).

The thing is that some clocks randomly report being hidden by Qt or by Windows, and self.show(). self.setvisible(True), self.raise_() do nothing. Neither showing them through the win32 api works.

So I can't fix that. I've tried porting to Qt6 and it has the same behaviour. Sorry guys, I can't fix this

[marticliment]

Hey, i've fixed this!!! See #123.

Fix coming with 2.2