Heh - strangely enough, my Quake-name was Exile - ahh, for the good old days of QTF . . . /me fingers his rocket-launcher and grenades in fond remembrance
GreenReaper
I'm not sure if this is what you're talking about or not, but it's worth a shot . . . there's a feature that skin authors can add that cuts off part of the borders when a window is maximised. You can stop this happening by either editing the skin's UIS file and removing all the MaxBorderCut attributes, or by adding the line SizeLimit=1 to your wb.ini file (in the Windows main directory). If this isn't it - then your problem is one I haven't heard of. Are you possibly running any other a
Oh, and just to forstall any cracking attempts, it was in display name alone - just the fame and fortune without any of the super-powers and huge responsibilities that go with it. *g*
/me recalls fondly the few hours he was Admin (yes, I cheated - wonder if they fixed that . . . )
nonicky: Try the WB3 fastload fix at http://www.windowblinds.net/default.asp?page=download - or update to the latest registered version if you are a registered user by entering your email at www.stardock.com/support If that doesn't work, try adding a link to wbload.exe in your Startup Start Menu group.
Indeed, kenray is perfectly within his rights posting a conversion of his own work. People aren't going to go looking through the Winamp skins looking for one they like, then convert it - that's too much hassle. They'll be looking in the WinMedia section.
You don't have to. If you have WindowBlinds 2.x it should work fine, and if you bought it recently you may be entitled to an upgrade - see www.stardock.com/support/ If you don't have WindowBlinds 3.x, XP-specific skins should still work, but without the XP stuff.
As far as I know, there is no valid upgrade path from WB 1.3 to WB 3 - there used to be one from WB 1 to WB 2, but that was over a year ago. Looks like you'll need to get the whole thing.
Then make an option so that it *doesn't* move it to the top. I've been asking for this for quite a bit. I'm now afraid to make an update for fear of being called a d/l-grabber. This has to be solved.
YHBT. YHL. HAND.
Of course, if you have a particular submission you think has been overlooked, and want to bring it to the attention of the admins, I'm sure a small . . . _donation_ to *cough* "WC running costs" wouldn't go amiss, if you know what I mean . . . *looks meaningfully at the empty collecting tin*
Yes, I think so. At least, they probably won't crash too badly if you put them together. Getting them to work together *well* (and looking good) is probably another matter.
Yep. The GIMP also has a lot of useful image filters for this sort of thing. It's a thing artists have to do quite often, so the tools are well-developed.
No. It *is* possible to create a brand new .msstyle. However, TGTSoft have *not* created their own skinning program (although they'd love to give you that impession) - rather, they have a program which patches one of the system DLL's so that you are allowed to use your own unsigned visual styles with the MS XP skinning engine (that handles Luna). StyleXP isn't original in that it adds nothing but the ability to use non-approved styles - MS didn't allow it in the first place because of many known
Actualy, AFAIK that area is still not available for skinning.
I'd really miss having no sounds in my skin (that's why I kept pushing Neil to fix 'em in UIS1/1+ ). I say do keep them short, but put them in - the user can always turn them off. Size is an issue - but the effect can be minised by converting to suitable format (22k, mono is usually good).
If it's been going on for that long, it's really likely to be another accessory that's interfering. Have you been running anything else that long, aside from Windows itself? And can you specify some skins for which it specifically does *not* occur (so that we can figure out what feature may be causing the problem)?
Could you give some examples of the skins on which it occurs and those which do not cause the problem? It may well be that they share some skinning feature (like menu skinning) that is causing the problem. Also, are you running any other accessories that might be "helping"? There have been a few bad interactions in the past . . .
Right-click/Properties/Appearance/WindowBlinds/Per Application/Add per-app setting... Just add the ones you *don't* want to skin and set their per-app setting to be "Exclude this app and do not skin it".
From what I overheard on #stardock I believe this was intentional (to make things _more_ readable), *however* it's certainly messed me up - things don't fit into the sections on 800x600 (eg the number of skins is not visible).
Erm . . . no, jb. They're there because they have additional XP stuff, not because they *only* work on XP. And I think you mean the "WindowBlinds" section - indeed, all the skins in there will work on all OS's as well.
WinXP skins have Windows XP-specific sections. This does not mean that the won't work on 98 - they work fine - it's just that you won't get the XP taskbar and panel. If you want that, you should take a look at some of the XPalike ObjectBar skins.
OK, it's WindowBlinds. Once you've downloaded it, if WindowBlinds is installed, it should be automatically loaded into the skin list. To apply the skin, go to Display Properties and then to the Appearance tab if on WinXP, otherwise look in the Skins tab. The skin list should be the first combo box on the left. If the skin is *not* there, go back to the website and right-click the download link - select "Save to file..." and put it somewhere you can remember. Then go to the dialog as abo
You have to browse to the place where you installed IconPackager and select the IconPackager .exe file. Alternatively, just run IconPackager and select the .ip file.
Yes. *If* you want your skins to be usable, this is a very bad mistake to make. Buttons should be big. They should be easily identifiable. They should be in a consistent position. The should do the same thing every time. Sure, you *can* put buttons wherever you want, and in many cases (like rollup) it may be desireable to separate them from the regular ones to avoid confusion, but overall, if, say, the close button isn't clearly marked, users are going to be lost. Again, as others have