Link to SkinStudio not working

I can't get Skin Studio to edit the currently installed skin. I open WindowBlinds Configuration, right-click on the skin currently installed, pick Edit in Skin Studio, but nothing happens.
2,309 views 7 replies
Reply #1 Top
Since you didn't say... I gotta ask....
do you have Skin Studio installed?
Reply #2 Top
Yep, I do. I just this minute found out what was wrong - you have to configure SkinStudio to tell it where default skin folders are or it won't work at all. I only discovered this by trying to start it as a standalone, just to see if it was working at all.

Needless to say, NOT putting a notice into WindowBlinds OR not having SkinStudio pick this info up on its own from Object Desktop config files is just plain dumb. At the very least, doing this would save Stardock (and its users) lots of time and frustration.

Reply #3 Top
You could open SkinStudio select Tools-Windowblinds-Open Current Skin. That's the way I open skins.
Reply #4 Top
you have to configure SkinStudio to tell it where default skin folders are or it won't work at all.

That's odd, I've never had this problem...

Reply #5 Top
Well, it's truth. The default skin folder was set to a non-existent path and clicking the Edit Skin in SkinStudio button did nothing visible at all. You should be able to recreate the scenario, if you really want to.

Reply #6 Top
I believe you, but I don't know why I would want to recreate that senario. All I'm saying is in all the years I've used the WB, and SkS (formerly BuilderBlinds), I've never seen SkS lose track of the WB folder. And I've never heard of it happening. Did you install WB in a non-default location?


In any case, I'm glad you got it sorted.

Reply #7 Top
Just as a closing word- OF COURSE I installed it in a non-default location. If given a choice, I never install apps onto my C drive! If I did that, I'd have to have a 500 gig C volume and defrags (if possible at all) would take all day. Not to mention what would happen to you and truckloads of data if something munges the boot drive. -- so, I have to assume that it's my native talent at breaking software at work here. Kosati, I will assume that you simply didn't think deeply about the question rather than the alternative  :LOL: