-
-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] 3 Monitors clock in the middle of main screen v1.9 #40
Comments
could you send me a screenshot of all your desktops with the clock where it shows please? |
like this: #32 (comment) |
https://drive.google.com/file/d/11IcdQBZOha6bABQKP3zIfKBEwW4gXECM/view?usp=sharing Please try this file and send me the output |
[WinError 259] No more data is available |
Disconnecting which monitor made elevenclock work? |
If I disconnect monitor three (far right) it works. If I disconnect monitor 1 (far left) it doesn't show at all |
Could you try this one? https://drive.google.com/file/d/11Or6IBtLF9qs23vicNgBaHQQN4U_lBBs/view?usp=sharing |
Same issue, still in the middle. It seems from the output that the clock geometry has the correct coordinates? WinError 259] No more data is available |
Yep, this is right. The point is that the coordinates of the clock after being moved to it's specific place are correct, but for some reason the clock doesn't actually move. I have found that all of you having this problem have multiple displays like "\.\\DISPLAY1" and "\.\\DISPLAY3" with the "\.\\DISPLAY2" missing (because you don't have any other display connected in that port/output). Instead, on people who have all displays without having one missing, it works. I've been looking and it looks like there's a Qt bug, so now i'm gonna try moving windows with the Win32 API rather that using QWidget/QMainWindow.move(x, y). But I don't really know if i'll be able to fix that... |
Could you try this version please? In this version clocks are being moved by the Win32 api, no QT... https://drive.google.com/file/d/11OzV36cSIVpjuuCp604IR1hsg51fhXNM/view?usp=sharing |
It shows on Display 1 (monitor number 1 on the left) but not on monitor 3 on the right (Display 5). It doesn't show in the middle anymore I have the 3rd monitor plugged in via a usb-C extension, could that be an issue? |
I don't think USB-C should be an issue... Could you send me the log of the last file i sent?
I don't think USB-C should be an issue... Could you send me the log of that time? |
[WinError 259] No more data is available |
I think i found what could be hapening... |
Could you try this one? https://drive.google.com/file/d/11bpL5RKT5fgjbHvhS9S1-3UInmmjVn7i/view?usp=sharing |
Still the same [WinError 259] No more data is available |
Disconnecting display 1 shows on display 5 |
Ok, i've done my best. I've added a switch. The default clock positioning behaviour will be same as before, but now there's a switch on system tray icon to enable win32 api and get at least 1 clock on one of the secondary widgets, because the other one closes itself due to a bug. To have the fix: Install THIS version: https://github.com/martinet101/ElevenClock/releases/download/1.9/ElevenClock.Installer.With.Alignment.fix.exe To switch between modes, you will need to:
|
With 3 monitors the clock still appears in the middle of the main monitor. Disconnecting one fixes the issue.
Console output:
[WinError 259] No more data is available
yyyy/MM/dd
h:mm tt
%#I:%M %p
%#I:%M %p
%Y/%m/%d
Starting update check
<PySide2.QtGui.QScreen(0x1f463a91ee0, name="\\.\DISPLAY2") at 0x000001F464AA53C0> PySide2.QtCore.QRect(0, 0, 1920, 1080) (1920, 1080, 96.0, 96.0)
This is primay screen
<PySide2.QtGui.QScreen(0x1f463a91be0, name="\\.\DISPLAY1") at 0x000001F464AA5740> PySide2.QtCore.QRect(-1920, 0, 1920, 1080) (1920, 1080, 96.0, 96.0)
PySide2.QtCore.QRect(-108, 1032, 640, 480)
start
Full screen rect: (1920, 0, 0, 1080)
Focus screen rect: (104, 104, 1097, 623)
<PySide2.QtGui.QScreen(0x1f463a91d00, name="\\.\DISPLAY5") at 0x000001F464AA5840> PySide2.QtCore.QRect(1920, 0, 1920, 1080) (1920, 1080, 96.0, 96.0)
PySide2.QtCore.QRect(3732, 1032, 640, 480)
start
Full screen rect: (1920, 0, 3840, 1080)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
Focus screen rect: (104, 104, 1097, 623)
The text was updated successfully, but these errors were encountered: