You need to use the "Restore Default Icons" in IconPackager to get your old ones back, before you uninstall. Installing and restoring should work.
GreenReaper
/me still uses notepad SkinStudio is useful for generating reference documentation, though.
And it will only skin them on XP - earlier versions don't have support for it. The shareware version does not skin buttons in any apps that MS itself does not skin them. It *should* skin the min/max/close buttons on everything - if that's not happening you probably have something like CommonNames interfering.
WindowBlinds skins windows. On XP it can also skin the XP taskbar, so in this specific case having OB is not necessary - just use WB with a Luna-style XP skin. ObjectBar can do a lot more than WB can do in the area of bars, though, and is more flexible, and of course it does it on all versions of Windows (so you can have the XP look on 9x).
Erm, no, the shareware version should work with all skins (although not all features will work). Try the patches at the WB download page off www.windowblinds.net
Of course, WindowBlinds comes with Object Desktop, which some would say is worth the $50 on it's own.
You might have to press enter instead (I think the double-click would select just one).
You have to enter the information that you were emailed into the "User Information" page, and click the Update Configuration button before the CM will work. If that doesn't work, contact sales or [email protected]
s/almost/always/ :-p
/me notes that making a new plugin was almost an option. Actually, I had one sort of ready (transperiser with memory for each program), just couldn't get a skin going with it in. Maybe in a few months. ;-)
Yes, that's basically it. *g*
There's a new public version that's meant to be out very very soon now . . . there'll almost certainly be an announcement on the front page when it's released.
> The key work here is "intended" > ...Good Intentions pave the road > to...well, you get the message. I get it, but what more do you want? For example, there has never been a stable feature set for WindowBlinds - users have always pushed for more features. Sometimes I get annoyed that bugs are not fixed, but I understand why. I would be much less pleased (and Stardock would be selling far fewer copies) if, for example, WindowBlinds was perfectly stable, but didn't skin any of
I don't know for sure, but that is probably an embedded DXScript object. It would probably require writing a little code to implement, but one of the DXScript programmers could probably release it as an object, so anyone could use it. Possibly ask around the DesktopX newsgroups to see if someone there knows how? As to the shadows, that looks to be the next version of WindowFX (coming soon to an ODNT near you, hopefully).
Yeah, yeah.
The release versions *are* intended to be completed versions. If you are having any specific problems with them, then you should indeed contact Stardock's support through the indicated channels (eg [email protected]). Alternatively you could ask here, or in the appropriate Stardock newsgroup(s) at news://news.stardock.com/ - so far, all you've said is that they act like beta programs - how? The releases every day/week are *not* to be considered "releases". They would normally be rest
You can indeed purchase by money order - email [email protected] and they'll tell you how. SkinConvergence == WinStyles, which is out now - you can try it at https://www.stardock.com/products/winstyles/download.html
Incidentally, many of the paying customers partly paid in order to get access to those betas, which is why they're an option - some people like to get their hands on the very latest components, even if they're not necessarily the most stable (sometimes they are, sometimes not).
No, those are released components. Your past experience is not correct, in this case - a and b merely mean that they are not the inital release (probably because a bug was found in it). Whether or not they *act* like "released" components is a matter of opinion, but they have been marked as such.
CommonNames, Logitech Immersion Desktop and other accessories that alter the titlebar and do not pass messages on correctly can all cause this. CommonNames must be installed - disabling it won't work, but ID only needs the iFeel vibration on mouseover of titlebar controls to be disabled.
guyguyme, please don't spam the board. You still haven't explained why skinners would want to have you do this in your previous post - if they're good enough to create the skin in the first place, they're more than capable of inverting it themselves, should they feel the need to.
That section, the toolbar background, will only be skinned correcty if you add the toolbar, toolbar background *and* rebar sections. Also, it is only skinned on XP.
That was . . . disturbing . . .
. . . except that people might think they only work on XP.
It is an issue. It is . . . discouraged. But really, it needs fixing. A simple "don't put this skin on the New Additions list" option would do - then people would have no excuse if they did make small updates and poked them to the top.