Kylde Larsen
Всего сообщений: 7
Дата регистрации: 16.11.2015
|
Создано:
15.04.2017 22:09:32
|
Dual monitor display, Win 10 64 Home Creators Update, Classic Shell (4.3.0) & WindowBlinds WindowBlinds 10.6 (042 - Windows 10 Edition) - 64 bit OS installed (both current versions), AWM 8.10.2 The taskbar on monitor 2 is graphically corrupted. The clock is black-on-black. Uninstalling Classic Shell & selecting the default (Microsoft) theme in WindowBlinds makes no difference
I found a similar problem here:
Edit, upgrading AWM from 8.10.1 to 8.10.2 fixed the invisble start button
|
Bogdan Polishchuk
Администратор
Всего сообщений: 4113
Дата регистрации: 04.04.2012
|
Создано:
16.04.2017 00:16:46
|
Kylde,
| Цитата |
|---|
| upgrading AWM from 8.10.1 to 8.10.2 fixed the invisble start button |
Could you name the exact number of your Windows build (type winver in the Search field of the Windows Start menu, press Enter. The Window containing the build number will appear).
Could you temporarily close WindowBlinds, disable auto-start option for this program, reset the computer and see whether the problem with clock appears when WindowBlinds is not launched?
Best regards.
|
Kylde Larsen
Всего сообщений: 7
Дата регистрации: 16.11.2015
|
Создано:
16.04.2017 21:53:05
|
| Цитата |
|---|
Bogdan Polishchuk wrote:
Could you temporarily close WindowBlinds, disable auto-start option for this program, reset the computer and see whether the problem with clock appears when WindowBlinds is not launched? |
This is how the clock looks on the 2nd monitor's vertical taskbar with WindowBlinds enabled
This is when you mouseover the clock:
and this is with WindowBlinds disabled:
and this is my Windows version (15063.138)
|
Bogdan Polishchuk
Администратор
Всего сообщений: 4113
Дата регистрации: 04.04.2012
|
Создано:
20.04.2017 19:10:21
|
Kylde,
| Цитата |
|---|
| The taskbar on monitor 2 is graphically corrupted |
Best regards.
|
Kylde Larsen
Всего сообщений: 7
Дата регистрации: 16.11.2015
|
Создано:
21.04.2017 03:48:32
|
| Цитата |
|---|
| This problem has been confirmed and it happens because of some incompatibility between WindowBlinds and Actual Window Manager. We'll try to improve the compatibility and will post in this topic when/if these problems are fixed. |
Thank you, I appreciate your dedication to your product
|
