Reply #2 Tuesday, December 20, 2005 1:52 PM
Reply #4 Tuesday, December 20, 2005 4:21 PM
scorpio logic...I have experienced all the things you mentioned. I wasn't sure about the fonts but I am now that someone else mentioned it.
I got an email from a little birdie (Thanks again little birdie
)It was suggested that I exclude Skinstudio in windowblinds exlusions. Skinstudio was already in the list so I figured what the heck, lets give it a try. I removed SKS from the list and everything seems to be working better. No crashes yet. It seems to have cleared up the font problem too. Go figure.
Still a slow startup though. Thats no biggie as long as I remember to wait. It's not as easy as you think when you have opened Skinstudio a million times before.

Reply #5 Monday, December 26, 2005 4:21 PM
Nothing has changed. SKS still crashes very frequently. The newest build of Windowblinds doesn't seem to have any effect. It is quite slow changing skins now.
I am losing my scrollbars more frequently. A reboot, load XP default skin and then back to my skin fixes it. My taskbar goes 3/4 classic. The areas where quick launch and taskbar buttons changes to classic. The start button and system tray stay skinned.
Would appreciate any feedback.

Reply #6 Tuesday, December 27, 2005 2:16 AM

Reply #7 Tuesday, December 27, 2005 6:11 AM
In case this helps... active and inactive windows are not painting properly. A window will be partially painted until I move a window over it and then it will be ok. It paints very sloppily. 1/2 active and 1/2 inactive until a window is passed over it.
Quite often when selecting a color using the "capture color" tool, I get a not enough memory warning and I have to close out SKS using task manager.
Font setting are still not being saved when saving a skin.

Reply #8 Tuesday, December 27, 2005 9:19 AM
The problem you are describing happened to me sometimes when I was using firefox which seems to be leaking like there was no tomorrow but since I switched to Opera all my resource problems have stopped. Can you tell me if you're running Firefox on par with SkinStudio? Also thanks for reporting the depraciates in the default skins. I'll correct the problem and we should have a new build as soon as Kris gets the cxhance after coming back from holiday.
Reply #9 Tuesday, December 27, 2005 11:02 AM
Think I'll hold off a bit longer.
I'm not trying to bring up the warez thing, NT, but it's a bit disheartening to hear some of the same symptoms being described for legit users as the hacked version users got.

Reply #10 Tuesday, December 27, 2005 2:16 PM
Skinstudio... I only use Internet Explorer 6. No other browsers installed. However, there may be a link between IE and Skinstudio. I had my hunches that opening IE with SKS running was adding to SKS crashing. It is only a hunch based on the timing of the crashes. Excluding SKS in WB options doesn't help at all.

Reply #11 Tuesday, December 27, 2005 10:30 PM
SkinStudio, when will we see the final (non-beta) release. I think I would like to wait on that build before I install. A first for that .. I usually always install the betas. But you know what they say: "Once bitten, twice shy".

Reply #12 Wednesday, December 28, 2005 6:12 AM
Reply #13 Wednesday, December 28, 2005 6:53 AM
dread using SKS anymore. Nigh Train, I have been experiencing
the exact same problems you describe running SKS.
At this point, Notepad seems to be the only solution for me.
Adam needs to fix SKS .... the sooner, the better.
Reply #14 Wednesday, December 28, 2005 7:04 AM
of SKS that can say they are NOT having the problems Night Train described
above (crashes, slows to a crawl, doesn't paint properly, etc)?
Reply #15 Wednesday, December 28, 2005 8:38 AM

Reply #16 Wednesday, December 28, 2005 1:36 PM
How many skins have you got open and how much memory do you have?...
I've just been messing with SKS for over an hour, having numerous skins open, making changes, saving, applying etc and cannot reproduce any of the problems noted. However...
I noticed each skin open added 30Mb to memory, and once I had about five skins open just moving the cursor around caused my CPU to get to 50%+. I also note I cannot exclude SKS from being skinned... so maybe this is a WB5 problem with painting the SKS UI???
Reply #17 Wednesday, December 28, 2005 7:43 PM

SKS was by default included in the WB exclusions but still continued to paint SKS. I removed it from the exclusion list and then re-added it and it stopped painting SKS. It was classic and so was photoshop and paint shop pro. SKS still continues to crash though. Odd thing is , in the past I have added or removed SKS from the exclusion list and there was never any change. Now, for the first time (that I remember) it paints classic when added to the list.

Reply #18 Wednesday, December 28, 2005 9:38 PM
One skin active ... sometimes two .... three is a no-no.
System memory not an issue.
Reply #19 Wednesday, December 28, 2005 10:31 PM

Reply #20 Wednesday, December 28, 2005 10:59 PM
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!







Reply #1 Tuesday, December 20, 2005 1:20 PM