Windowblinds 7 Crack Keygen Download
Phillipp Schneeberger
Hi, I use WindowBlinds to skin my window borders but it seems to break with startisback. Applying a windowblinds theme will make all startisback elements glitch, the taskbar is all glitchy, windowblinds skins the taskbar and it seems like they conflict, but the start menu is just text and some very glitchy black boxes where the menu textures are supposed to be, the jump lists on the taskbar are black box where the text is supposed to be. I am wondering if this can be resolved, as I love windows 7 look and I don't want to buy start10 from same developer as I like startisback more. Any way to stop the glitches or disable one of the programs from skinning the taskbar. No process is there for startisback so I can't exclude it in windowblinds. I posted on windowblinds forum but decided to post here too if anyone can help.
Yeah, I remember giving WindowBlinds a try with StartIsBack relatively recently. Far as I can tell there's nothing you can really do unless one side or the other patches support for the other. My recommendation is to go with another Stardock application, Curtains, which is similar in concept to WindowBlinds but way more configurable and compatible with things. I'm using it and it works perfectly with StartIsBack.
Your best bet if your set on using WindowBlinds is to use it with their start menu replacement software, Start10. You could also try your luck with Open Shell, but iirc that had the same issues with WindowBlinds as StartIsBack.
Naturally it'd be nice for support between the two to be added. However, for now, my advice is to seek out a different combination of software, as these two applications just plain aren't going to work with one another in their current iterations.
Also, Stardock Windowblinds and Start10 uses .bmp images to generate their theme images as .msstyle themes generally use .png images which is why StartIsBack probably acts glitchy with Windowblinds. Stardock has made it that if you want to use Windowblind themes you have to use Start10 and I don't ever see that changing, it would be detrimental to their sales of Start10.
Does anyone else have an issue with using the latest windowblinds 7 build on win7 with Opus 9 or Opus 10?
Specifically when opus prompts using certain explorer dialogue windows, the bitmaps are all wrong and messed up, see attachment for an example.
I had this issue with opus 9 and thought it might be resolved in v10. Disabling Windowblinds or excluding opus completely fixes the issue, but it doesnt look nice...
The area where things are wrong in your screenshot is where the standard File-Open dialog has a glass background, which makes me suspect the theme and/or Windowsblinds doing something wrong with the glass (or what the dialog things is glass) area of the window.
appreciate your comment, however, as I have said, the issue is not theme specific, happens with other users and is irrespective of windowblinds version.
All other explorer dialogues appear fine when launched from other apps. Only Opus has this issue.
WindowBlinds works by hooking into Explorer. Since Directory Opus is an Explorer replacement, there's nothing WindowBlinds can properly hook into. It's not so much a bug as an incompatibility. Going forward, I would suggest keeping the program in the exclusion list.
In the case of the problem you've found, Opus is just showing a standard File Open dialog and should be the same to WindowBlinds as any other application showing a standard File Open dialog (e.g. Notepad).
well, seems like I might be the 'middle-man' in getting to the bottom of who has the actual issue here.
I'll feed this back to Stardock, however, I fully expect a 'this is not a windowblinds problem' type of response.
Opus may be unusual in that it's using parts of the Windows theme that few other apps (except Explorer itself) use. e.g. The breadcrumbs path field is drawn using special elements that come from the theme.
I just happened to see this topic and had a look. I am using WindowBlinds 7 on Windows 7 x64 SP1. I never even noticed this when I registered so I had another look and sure enough I have the same problem. But I completely disagree with leo when he wrote that they use a standard open file dialog. After looking at a number of other open file dialogs on my machine I found that DOpus is the only one that contains a non-standard open file dialog even without regard to WindowBlinds.
I have attached two images, one is the DOpus dialog and the other is a standard dialog, this example is from Snagit 10. it looks like the DOpus dialog is an attempt to duplicate the newer standard dialog rather than actually using the standard dialog.
The fact that it looks different in Opus on your system appears to be coming from some difference in the way you have WIndowBlinds (I assume) configured to modify Opus. Look at the Okay/Cancel buttons in the Opus dialog and note they are not themed. None of Opus is themed in your screenshots in fact. My guess is WindowBlinds (and or how you have configured it) is making Opus run in some kind of unthemed / compatibility / old-style common-controls mode and that is why the dialogs look different.
See the dialog in my screenshot near the top of the thread for what the dialog looks like coming from Opus on a standard system. (And no, Opus is not detecting WindowBlinds and hiding the tree or doing anything weird with the dialog; it's just showing the dialog. Seems that WindowBlinds is treating Opus differently to other programs.)
I agree it would be silly but people do this all the time. After trying this with the default Aero theme it does seem to be the standard dialog. I will eat my hat now. I have attached the same screenshots I posted previously only with WindowBlinds turned off and the default Aero theme applied.
WindowBlinds has some odd behavior in some applications. Its basically something you have to live with. Sometimes it is because applications do not use standard controls or make use of system preferences. So I admit, WindowBlinds cannot be absolved.
And just like I should not have jumped to conclusions about your use of a standard dialog I don't think you should make assumptions about what WindowBlinds is doing to DOpus until you have actually used it and had a developer try to figure out why the dialog looks strange. As a developer, that would be my knee jerk reaction to the problem but I am not thinking about business justification for such an effort.
I thought it unfair to write that I tried it on 15 applications without indicating which applications I tired. So here is a list of 15+, all of which have no problem displaying the file open dialog when themed with WindowBlinds 7. Just pointing it out.
Opus is just telling Windows to show a standard dialog. Opus does not draw any of that dialog itself, it just calls a function and Windows takes over until the dialog is closed, then control returns to Opus, which just reads a filepath that's given back to it.
So, please, if you want to post about this, do it in WindowBlinds' direction. It's completely outside our control and we have no idea, nor way to discover, what WindowBlinds is doing to our process or the OS in general.
I think it's rather unfair for you to just blow us off like that. This is a problem, plain and simple. The only app on my system that doesn't display properly with Windowblinds is Directory Opus. Its Open dialog is messed up as demonstrated above, and certain skins don't display the menu properly, as demonstrated above.
Let me reiterate that Directory Opus is the ONLY app that demonstrates these oddities. Directory Opus clearly does things differently than the vast majority of other Windows apps. Saying that the problem is not with Directory Opus is not a very nice way to skirt around the problem.
There are a lot of MacOS X ones but many of them I don't personally care for because they took their images from screenshots rather than rendering their own images (this shows up on buttons the most).
Hehe, I happen to like windowblinds even though i dont use it. If Rhodium edge, Sosumi, Prophecy, Br2k1 v3 (if it ever gets released :D :D ) and Static (Xcert's new theme) ever get released on windowblinds, I'd probably be over in a second, but until then, I'm happy with msstyles and there isn't really anything thats got me sold over on the Stardock side of things.
I've pretty much given up on the XP Start bar at this point and have moved almost exclusively to ObjectBar to take it over because of the smart menu support which XP (in a fit of MS insanity) dropped support for.
There are a lot of MacOS X ones but many of them I don't personally care for because they took their images from screenshots rather than rendering their own images (this shows up on buttons the most).
7fc3f7cf58