Windowblinds is a great concept...BUT?

from WinCustomize Forums
For the most part Windowblinds is a great idea for skin replacement but if you have ACDSee 4.0 you'll find the program won't open. If it works for you then great. As for other programs, it did take a little longer to open up Outlook Express and that was enough for me to say: "Ok it's time to get rid of Windowblinds". I'm hopeing down the road these glitches will be rectified as it is a great idea.
2,508 views 9 replies
Reply #1 from WinCustomize Forums Top
No problems here, everything works fine..........what OS are you using? Do you have suffient memory?
Reply #2 from WinCustomize Forums Top
I don't use ACDSee, but I've never noticed any slow downs with Outlook Express. Do you know you can exclude programs from being skinned? You can even set WB to only skin titlebars on certain programs. These features should make it usable for you. Several years and nearly 2000 skins later, I think WB is more than just a great concept. It seems nearly perfect to me.

Powered by SkinBrowser!
Elemental: Reforged
Reply #3 from WinCustomize Forums Top
I had ACDsee4 and WB working together OK..but it was shareware of a CD...so I just stayed with '3'...

'down the road'....almost sounds like WB must be 'new'...it isn't however...it's been around for quite a few years...and certainly a long way 'down the road' from its simple beginnings...
Reply #4 from WinCustomize Forums Top
ACDSee has licensed DirectSkin and is using it on some of their other programs with ACDSee being ne of the programs they're using it on. So obviously WB must work pretty well on ACDSee.

My suggestion would be to check to see if you have a virus scanner that scans every file that gets opened because that would definitely affect WindowBlinds.

Powered by SkinBrowser!
Reply #5 from WinCustomize Forums Top
I have XP Home and I have used a lot of software through work and I have yet to find a program that opens slow due to WB.
Reply #6 from WinCustomize Forums Top
I've been using ACDSee for three years with Windowblinds. One of the first WB skins I made was done specifically to skin ACDSee (Darkmarble). I've never noticed any problem. Right now I'm using ACDSEE version 4 and WB version 3.4 - Have you tried using a UIS1 skin as a per-app for it?

Maybe there's some other problem, like frogboy said, or a video driver issue. I found that I could not run CursorXP with CorelDraw. It slows to a crawl and eventually locks up unless I unload CursorXP.
Reply #7 from WinCustomize Forums Top
I use ACDSee, OutolookExpress and WIndowblinds together for 3 and a half years now and never had one single problem, it seems to me that it maybe be a problem on your machine.....video card maybe?
Reply #8 from WinCustomize Forums Top
I don't use OE, but I have no problems here with WB and ACDSee 3 and 4.

Okay, that's not completely true.

I was having problems with ACDSee 4's path display in the copy/move dialog disappearing, whether using UIS1 or UIS2. I fixed it by changing ACDSee to titlebar skinning only. I never experimented to see if I could get away with less restrictive skinning.

Powered by SkinBrowser!
Reply #9 from WinCustomize Forums Top
I don't mean to but in... but I haven't had an issue with window blinds since like version 2.0.... I remember back when I first got it... I couldn't play solitaire... it would give me and error every time I tried to maximize it or move it... but that's it... I haven't had a problem with it... in years... he he he... yeah years...

Powered by SkinBrowser!