hello, is there any chance the vlc edge drawing bug reported here will get addressed? I tried the WB beta .86 and it's still there. Windows 10 Home (19041.vb_release.191206-1406) WindowBlinds 10.86 (061 - Windows 10 Edition) - 64 bit OS Window titlebar blur features are enabled on this operating system Wblind.dll &nbs
Well done! I am very happy to report that all the problems I highlighted have now been fixed. Thank you for the quick reaction! Greetings, gvse
Thank you for the reply! I really appreciate the quick reaction. Good to know the bugs are going to get addressed.
Hello since the update 10.83 I have observed a number of bugs connected to faulty painting of theme elements. The bugs occur in my own theme as well as default themes that come bundled with WB. 1. backgrounds of buttons that select different view styles in explorer fail to paint. <a href="http://www.mediafire.com/file/utpdgsndmvd56
I have the same problem. Reported it here a long time ago and was advised to disable WB for vlc. Hope this gets fixed as I'd really like custom WB themes to be applied to vlc as well.
[quote who="LightStar" reply="1" id="3749313"] Since it wasn't mentioned, this release fixes the white background issue in the explorer tree area on WIndows 10 v1809 and higher. However, skins designed for Windows 10 before SkinStudio had settings for those colors will still experience the issue. Any of my skins still having that issue will be updated over time. [/quote] Could you please let me know where in the SkinStudio is the section responsible for this part of the them
With the latest WB (10.74) VLC media player is still buggy: the right and bottom edges draw with artificats (black lines in my case), and on resizing the vlc window the artifacts start multiplying in the areas I mention above. Excluding vlc from wb skinning fixes the problem, but I'd love to finally have the app working correctly with WB. VLC: 3.0.4 Windows 10 Home (17134.rs4_release.180410-1804) WindowBlinds 10.74 (054 - Windows 10 Edition) - 64 bit OS Window
I already installed the update after going through the purge routine so there's not much more I can try. I had to revert now to the stable installation as working with a secondary display was proving too troublesome.
I've experienced another problem: when using 2 displays via Project/Extend commands in win10 the taskbar on my main display becomes non-responsive (buttons don't react to clicks), and it disappears almost completely from the secondary/extended screen (only the "TaskView" button is visible). Im on Windows 10 Home (17134.rs4_release.180410-1804)
Thanks a lot Vad_M! This actually works! I do have one issue left: how did you solve the problem of min/max/restore titlebar buttons in firefox? Mine are just gone when I apply the wb code [code="css"]#main-window { -moz-appearance: -moz-win-glass !important;} #titlebar-buttonbox > toolbarbutton { opacity: 0.0 !important; }[/code] I mean the native WB titlebar doesn't get applied to my skin. It must be something in my FF css, but I am at a loss what it could be.
VLC 3.0.3 is still buggy with WB skinning: the right side and bottom edge become corrupt once you start resizing the application (black lines get drawn). Also this causes duplication of some buttons. Also, once Firefox is enabled in WB you lose all possibility of skinning it via UserChrome.css as each time this file is overwritten by WB, reverting whatever changes you make there.
VLC 3.* Hi, there is a problem with the VLC version 3: when themed, the right and bottom edge/margin get extra fill with color, which gets corrupted (turns into black/dark gray) once you try to resize the window. I tried with various custom and default WB themes and the problem persists. It goes away once the app is excluded from WB skinning. Windows 10 Home (17134.rs4_release.180410-1804) WindowBlinds 10.65 (048 - Windows 10 Ed
That is correct. All Nvidia drivers post 380 release result in disappearing/flickering titlebar of PaleMoon while using WB. Yes, win10 (I provide detailed infromation in the thread I linked to above). I'll be very grateful for looking into this! Edit: I just double checked the link and it's not working. I am quite ok with using different forums and providing link but here it just directs me to this very thread. The thread I want to link to is here in WindowBlind
Thanks LightStar! I've just fixed the link.
This update still doesn't solve the problem I reported here: https://forums.stardock.com/482904/page/1/#3687725 . Is there any hope for a fix? I am getting desperate for some feedback as right now I am on an outdated nvidia driver.
Hello again, today I've downloaded WB beta10.64, the newest Nvidia driver, along with the uptodate PaleMoon browser (27.4.2), and the problem described in the first post still remains. Is there any hope for a fix in a future update? Let me stress that the flickering titlebar has been a problem ever since Nvidia released 380 driver, and the problem only occurs when WB is running.
hello, today Windows installed the 382.05 driver on its own and the problem described above has returned. I can revert the drivers, but this is gonna come back soon. Have you guys looked into this? I needed to change my network connection to "metered" type to prevent the system from updating Nvidia driver. I'd really appreciate some feedback on this: is it even considered as a WB-related problem?
Hi, Since Nvidia updated their drivers to version 38* and upwards I get a bug in my browser of choice, PaleMoon: the titlebar starts to flicker (disappears and reappears) as I move cursor over sites displayed in browser window. This has never been a problem with previous drivers up to 378.92, which I am using currently to avoid the problem. In my troubleshooting I did the following: -used default PaleMoon skin and WB themes (my own theme and the ones shipped with
Stardock Forums
I have tried several different WB themes and PM skins with Pale Moon 27 and while renaming the PM exe to firefox.exe brings back the title bar, the painting of caption buttons (min/max/close) retains the size of default win10 buttons. Specifically, the buttons retain the size defined by a WB skin but their background covers the large area of default win10 buttons. Is it something that can be solved via future WB update?
Stardock Forums
Hi Neil, thank you for the tips! I went with option 2 and it worked with one exception: the background of min/max/close buttons is not skinned properly. It is now just color inherited from some element. Ill apply some other FF skins and see if it's perhaps an issue with my custom FF/PM theme. update: so after applying several other PM skins I see that the issue with the min/max/close buttons' background remains: it looks like that section
Stardock Forums
I updated Pale Moon to version 27 the other day, and now the title bar is not painted except when using default WB windows10 theme. Already posted at their bug section.
Hi all, I have installed WB6 on my vista machine and the minute I install and activate all is well, i.e. I get full per-pixel support on window frames. However, once I restart the system, I lose per-pixel support on windows: they get skinned using bmp images, and so are flat. All other elements are skinned properly. This problem sometimes (for no clear reason) disappears, however, 9 times out of 10 I am deprived of per-pixel support on window frames. I tried uninstalling, cleaning the regist
