[quote who="benmanns" reply="1" id="3592927"] Aero Glass (junkware) is not a Stardock Product as far as i know therefore your chances are slim to get proper support for it. I even doubt that you will get any support from the original creator of the tool. [/quote] Not only is Aero Glass an actual product, it's not "junkware", and is actively supported [has been since it&
I'm a bit baffled why you're trying to run aeroglass with WindowBlinds... WindowBlinds provides the same effect, does it in a much more efficient, and far cleaner, way. Aeroglass served it's purpose prior to WindowBlinds being released, but it's not an elegant solution, especially when WindowBlinds provides the same ability and more. To garnish the same effect in WindowBlinds, you'll need to use SkinStudio [I recommend the Windows 8 metro skin as the ba
Interesting... If you haven't already filed a ticket with Stardock, I would, as that's not normal. Just so you 're aware, it could also have nothing to do with Start10, so I'd recommend verifying your index by 1. checking if all indexing has completed or if it's still indexing, and 2. if indexing has finished and there's still a lag with results populating, I'd recommend re-indexing windows. Re-indexing will take several hour
[quote who="NossieUK" reply="52" id="3577511"] "If you utilized SkinStudio heavily while designing your custom skin for WindowBlinds, you may want to check out tutorials online about how to modify Windows theme files." Would suggest the issue was as simple as changing the theme itself. Oh it's not? Well then. [/quote] Really, because I'm certain I would have included that tidbit if it was the case, and considering i mentioned&
[quote who="NossieUK" reply="49" id="3577497"] is there currently a simple theme that works with windows 10? [/quote] Did you not read my reply to your previous post (reply #43)?
For users wanting the ability to skin Windows 10, but too impatient to wait for a WindowBlinds10 release: The ability to skin Windows has always existed, its just not a simple process of opening up an application, pointing, and clicking. If you utilized SkinStudio heavily while designing your custom skin for WindowBlinds, you may want to check out tutorials online about how to modify Windows theme files.
[quote who="NetBadger" reply="46" id="3577472"] On July 30th, I installed the official release of Windows 10. I made the mistake, that I expect many others made of quickly reading through the forums. I saw some post about Windowblinds 8 working on Windows 10, and did not read the official Stardock section, saying that it didn't support it. I had kept mt Object Desktop subscription, in force from its inception until last year. This time around, I just bought Wi
@Sosiosh There's one small difference Start10 adds to the Win10 start menu, and I'll post back later what it is, that might make it more convenient for users. You can still utilize the Win 10 start menu with start10, just select the option for the default win start menu on the main settings page. Start10/ slightly modifies the location layout of the options on the left hand side of the start menu, which makes it more convenient for users.
@NossieUK There's more to it than just that, as Explorer backgrounds and toolbar backgrounds also render incorrectly. This isn't simply an application compatibility issue, there's been fundamental changes done in the coding of Windows 10 that make what used to work in Windows 8 not work in Windows 10 (this doesn't just apply to WindowBlinds, as simple RP creation vbs scripts no longer operate with arguments used in Windows 8.1 and prior). Many users
I'm not sure either considering I've never see an application windows refuses to install work the way it's supposed to if then installed in compatibility mode. Windows 8 has been touted by a lot of PC journalists as a more refined Windows 8.1, and while that may be true from a GUI/user experience perspective, it is most certainly not the case from a coding perspective. You have to look no further than simple vbs scripts for creating a restore point, which work
Reading is always a good place to start...
...
Using WindowBlinds8 on Windows 10 will be a personal choice for every user, however, considering the Taskbar is a focal point on every computer, the broken gui is enough to where most will prefer to not utilize it. Couple that with the fact the taskbar is meant to be a central hub in Windows 10, with Cortana and Virtual Desktops, you're creating problems with those experiences. I've used Windows 10 since Dec and the broken GUI is simply a non starter for me (as it will be
Right, because it's not compatible with Windows 10. If it was a general application, compatibility mode would suffice, but due to the deep hooks DWM has in Windows 8/8.1 and Windows 10, Windowblinds is not an application that should be ran in compatibility mode, as the gui will not render correctly (it goes beyond the taskbar, and you'll notice other incorrect renderings as you utilize Win 10 10240). What about boot times, notice a difference? If you run Windows 10
A lot of code has changed in Windows 10 (especially within the GUI), so its doubtful WindowBlinds 8 will ever work properly on Windows 10... the logical conclusion is WindowBlinds 10 will be released, much as WindowBlinds 8 was released for Win8. To demonstrate just how much code has changed, a simple restore point creation vbs script for Windows 8/8.1 does not work on Windows 10. Upgrading an existing 8.1 install to RTM build 10240 [Win 10] with WindowBlinds 8 installed
IconPackager is great... if and when it works/applies itself correctly. Icons very rarely ever apply the way they're set, and when they do, saving and re-applying the same package causes a cluster f*** of the wrong icons associated with the wrong files and folders... then to make it worse, applying the default win package doesn't fix the issue. Great concept, horrendous application on Windows 8/8.1, as it appears Stardock has consciously decided to stop actively supporti
I have no problem doing that again... but I believe (if I recall correctly) a few other users have reported the issue over the last year or two. At first, when it happened after I upgraded to Windows 8 (the week it was RTM), I thought it was a problem unique to me, so I performed a clean install of Windows 8, installed drivers in the proper order, installed Comodo Internet Security, then installed the software I use via Object Desktop Manager. As soon as my laptop resumed from s
Is it possible to apply a WindowsBlind theme via the Command Line? The reason for asking is WindowBlinds never resumes from sleep or hibernate properly, always resetting the ui color to black (in the theme is cyan). It would be helpful if I could create a batch file or vbs script to run automatically after resuming from Sleep or Hibernate, as I must also shutdown (end process) the Desktop Windows Manager (due to WindowBlinds apply causing rainmeter skins (ini's) to load impr
As far as Rainmeter goes, there's two versions on their site, 1 a stable release [.31] and a beta version [.32]. I've used both and I haven't noticed any stability difference with any of the INIs I run. I've included a screenshot to show how many INIs I have running (everything except the Comodo widget is Rainmeter), along with the Task Manager showing Rainmeter @ .6% CPU usage. It does occasionally go as high as ~3.5%, however that's the highest usage I&
If Rainmeter is heavy on resources, something else is going on as Rainmeter, by design, consumes a miniscule amount of resources and is entirely dependent on INI files. I'll post a screenshot of my desktop later which shows a massive amount of ini's loaded (all of which are auto updated every .5 - 60 seconds) with a 0.6% CPU load and 26.9MB of memory. If it was a while ago, it could very well have been a bug that has been fixed. While Rainmeter does take a bit
[quote who="zorlack" reply="4" id="3510392"] Hi, unfortunately those settings in the registry already are at 255. It looks like the TClockEx superseed the settings of the taskbar's system tray transparency albeit there are no settings within the app. [/quote] A few thoughts... and two questions: What OS are you currently using and if it's windows 7/8.1, why are you still using TClockEx? From all appearances, TClockEx is a piece of software d
[quote who="zorlack" reply="2" id="3509698"] Thanks jmonroe0914 but the goal here is to prevent transparency for the clock. I am not trying to make the taskbar transparent. [/quote] I apologize, as I misunderstood... however, the same process "should" work. Instead of setting the value to 0, set it to 255. Also, if you&#
[quote who="gevansmd" reply="20" id="3509688"] What's odd is if I get a chrome popup window it is skinned properly. Otherwise it gets the standard chrome frame and buttons regardless of what blind I have installed. [/quote] The only thing I can think of is perhaps Windows 7 has something to do with it. I'm running 8.1 Pro, however if I get time, I'll try installing WB 8 in trial form on a Win 7 VM and see if I can replicate the issue. W
[quote who="gevansmd" reply="16" id="3509476"] On my PC Chrome is never skinned, no matter which nWB I use. I don't have it excluded in the "per application" tab. Should the WB frame and buttons be visible with Chrome? I'm running the latest WB and Chrome versions on Win 7 64 bit. [/quote] As Neil mentioned, the only part of Chrome that is skinnable is the title bar and window frame. However, there is a bug in WB 8 that c
[quote who="aeyquem" reply="3" id="3467781"] Any ideas on what could possibly be making the colors to change? [/quote] There is poor integration of WB into Windows 8.1 sleep/hibernate, and upon a system resuming from sleep/hibernate, this will occur. This is not user error but poor integration in Windows 8.1 and how WB draws upon resumption from sleep/hibernate. To my knowledge, the only way to fix this is either reapply the same theme or restart. If you ch