[BUG/ISSUE] Lock screen not undetected #1067
Comments
bayazidbh
added
bug
|
Hi @bayazidbh, here are happening three things:
(1). Did this help? |
marticliment
added
needs-author-answer
|
It does, thanks. Tbh, it doesn't bother me all that much once I disabled the hiding windows clock, but I did a cursory look at the Closed Issues and it didn't seem to be on the list of known issues/common problems, so I just wanted to report just in case as I usually would. Thanks for taking a look and tell me if you need more info. |
bayazidbh
changed the title
|
If you wish, since I see that some of the issues are with the transparencies when an app shows on fullscreen, there's an option that will remove your clock's background when an app shows on fullscreen, so only the text is visible: |
marticliment
changed the title
marticliment
added
ready-to-go
|
It doesn't seem to have any effects? Is there a way for me to export my settings just in case one of them conflicts with the transparent option? It does seem to blink for a second when entering/exiting fullscreen mode.
Oh, I do use four virtual Desktops, and AnyDesk is usually turned on in Fullscreen Mode on one of them. Could that compund the issue? Also probably why there's so many full screen event on the log (I've omitted them with a [...] when there's too many).
Fullscreen Event Log
(also, small typo on the issue title) |
marticliment
changed the title
|
You can import/explort settings from the About section: I see errors on your log, it might be because of that it does not work... Chores to do on this issue: |
|
Right, here's my settings (extracted with Notepad++), maybe there's something peculiar with it?
The only other thing peculiar I could think of is that I use StartAllBack with top taskbar placement and WinXCorner for creating hotcorner shortcuts for a few things (mainly Task/Virtual Desktop View). |
|
No, there shouldn't be any issues with WinXCorner. Thanks for the settings file, i'll take a look |
|
Hi, I'm currently using the v4.0.0, and the transparency effect works fine with StartAllBack now: Screenshot_2023-01-26_69.mp4However, I don't know if this is StartAllBack related, the clock is stuck transparent if the device is locked/unlocked: 20230126.100431.mp4The transparency requires a restart of ElevenClock to go back to being opaque. Purely speculation, perhaps it sees the lock screen as a fullscreen app, but since it's not actually an app it never detected the unlock as an app no longer having fullscreen. I can confirm that going to a fullscreen app and then un-fullscreen-ing them reverts the Clock back to being opaque, and it goes back to the same behavior as in the first video. So I suspect it is an issue with mistaking the lock screen as a fullscreen app and not detecting the unlocking to cancel that mistake. Log
langname: 'default'
|
|
if you were to set the clock to not be transparent when an app was in full-screen, this wouldn't hepen, right? |
|
Yes. I tested with fullscreen transparency off, and it's just fine. I also tested it with Hide Clock when full screen enabled -- the result is that the clock is hidden until I restart it or I did an un-fullscreen event, much like the fullscreen transparent behavior. So most likely something in the lock screen process tripped the fullscreen detection, but the unlock screen process doesn't trip the un-fullscreen detection, so it mistakenly thinks there's a fullscreen app but never get a signal telling otherwise. |
|
Ok, i will investigate this |
marticliment
changed the title
Chores to do on this issue:
Before submitting the issue
Describe the bug
Problem with ElevenClock always assuming taskbar and default Windows clock location at the bottom, even after manually moving its position to top, causing issues with transparency/blur layer effect not applied to the actual ElevenClock location while remaining at the bottom unless hidden with one of the work around fixes.
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
Working transparency/blur effects on top location and correctly assumes that ElevenClock's location as the Windows Clock's location.
Screenshots
Screenshots
Not-fullscreen
Fullscreen
(no transparency on full screen app)
The Log
Log
Additional context
A work around is enabling
Disable hiding the default windows clock, though transparency while in full screen doesn't seem to work. Hide for RDP/Citrix experimental option works with making the transparency/blur layer at the bottom be hidden when a fullscreen app is on, but otherwise doesn't work when there isn't any nor does it allow the ElevenClock to be properly transparent..Screenshot
Not-fullscreen
Fullscreen
The text was updated successfully, but these errors were encountered: