I gotta disagree with the Stardock "party line" concerning requirement / usefulness of HDR in Win 11. Win 11 supports it, WB11 does not, therefore WB 11 is not Win 11 compatible. I understand HDR compatibility was nerfed to fix another issue, so now it's really not compatible on 2 points. I'll continue to follow development, but don't tell us "you don't need that feature of your OS to buy our software".
Windowblinds config screen background goes black when HDR is turned on. Options can be moused over and highlight, but the text descriptions are unreadable (black on black). Win 11 and WB beta 007 or v9/28/2022.
I have excluded AutoCAD 2006,2007 & 2008 from skinnning at all via the Windowblinds properties dialog. Prior to v2006 I never had any problems. Which exe's have you excluded?
first, the required info. WindowBlinds version : WindowBlinds 5 (5.51 (build 97 x86)) WindowBlinds is installed correctly on this PC WindowBlinds appears to be activated on this PC Your machine supports per pixel borders on WindowBlinds skins. (ViewSonic VX910) 1 is attached to Radeon X1650 Series (Plug and Play Monitor) 2 is attached to Radeon X1650 Series Secondary Wblind.dll 2007/06/19 10:39:20 Wbsrv.dll 2007/03/13 09:
After insuring that the "load at Startup" was turned off in OD+ 1.9 I tried to simply copy the program group shortcut from the stardock group to the startup group as zubaz suggests. This resulted in the same double running of OD+. I also found the same 2 entries in the startup with MSConfig. Also had the same result of disabling one or the other disabling both. Searching through the registry I could not find either entry as listed in MSConfig. I disabled startup in OD+ again, and manual
I have the same double or nothing docks issue with OD 1.9. I installed the standalone package from the registration e-mail link. It was working well untill I checked auto startup option box. I find 2 entries in msconfig for odplus startup, one as user and one as common. unchecking either will cause none to load. Uninstalled and re-installed package from sd central with same bad results.
My suggestion: auto-flyout when hovering over your custom fly-out menus (like the weather dock does).
Thanks, for the heads up. Now that I've got it on the dock, can it auto-fly like the weather docklet? I must click it to get it opened.
I can create dock links to folders, but can't find how to make the contents flyout, only display as menu. I checked the readme for instructions but it has more artwork credits than useful information. I hope they have not been removed, it's why I purchased 1.9.
Thanks for the cache clearing tips MS. I will keep it in mind but I think that waiting for the next release will be my best bet. Keep in mind that this situation has occurred on 2 different systems. The OD free is the only SD app on either of them. I am a reg'd WB user but have quit using it long ago for other reasons. It was never installed to either of the systems in question. The fact that the error is repeated convinces me the issue lies with it, and does not speak well for
Last bit on this topic. The issue is not only with 3rd party docklets. I cannot change icon image on original SD docklets either unless the image is in the "program files" directories. Guess I'll hold off on purchasing plus untill v2.0. I was looking forward to the flyouts though
the one I mentioned allows me to change to what ever I want, wherever the image is stored Your shutdown app behaves the same way. I can only change image if both app and image are in the "program files" directories. As stated in previous post, still usable but wierd.
I have confirmed these results on both systems that I use and have OD 1.9 free installed on. I have always been placing the docklets in the "program files" directories of OD, never tried the "my documents" directories for them. Changing of docklet images only works when both image and docklet are stored in the "program files" directories of OD. While I can change application shortcut images from either library source, being forced to maintain 2 libraries is silly. I will just h
I have pushed further and resolved the initial issue of icon changes to the shutdown commands. Neither of the 2 shutdown docklets mentioned here so far would allow me to change the icon. I know where / how to do it, but the image would not update. It turns out that the icon(s) I want to use must be in the c:\PF\SD\OD\BUNDLED IMAGES directory. These docklets are not able to recognize or use the images if I have them in the \my documents\SD\OD Library. I do not know if t
MySecret, I am trying to use the same docklet, but I am unable to change it's icons via the usual properties dialogs. I have this same situation on 2 different systems. I did d/l the docklet independantly for each system, but from the same source (wincustomize). Can you post a link to the archive you have that appears to function?
I am currently using OD 1.9 free. The one thing it is missing (for me) are built in commands for shut down / restart / standby. I have found the docklet exitwindowsv1.2 which seems to provide the function, but the docklet will not allow me to change the icon image from the default question mark via the "dock entry properties". I know the docklet author must fix that. I am wondering if OD Plus will add any new internal commands to perform shut down / restart / standby and negate my need
I know it's a bit over the top, time will tell. On the subject at hand: I have been using links from SD support to acquire my wb file. I also see that I am not the only one getting a "mix of files" installed on their system judging from some of the posts here. Is it so hard to beleive the distribution file is incorrect? Too much to ask to have it checked?
I have done the uninstall / reboot / re-install (even deleted the directories) and obtained the file results shown. If the versions are mixed it is due to the archive I downloaded from stardock. I am looking at a format and re-install in the coming weeks. If you can e-mail me a link to a good source I will try it at that time. Don't take the folowing personally, it's simply more of a position statement. I am not using SDC. I do not wish to use SDC. I was an OD user in th
If I have a skin applied with WB 5.1 the program wuauclt.exe will crash when executed. I assume that it is Windows Update Auto Update CLienT. It manifests itself at sometimes at startup as a DEP error, but is usually a gpf popup when I am shutting down the system. I do not know if the gpf at shutdown error is really a startup error that never displayed until some other blocking process gets shut down. With WB installed, but not skinning all is well and I have wuauclt.exe running in the
Stardock Forums