Copyright: Stardock Systems, Inc.
Citation: Copyright 1997-1999 Neil Banfield and 1998-1999 Stardock Systems, Inc.


Getting Started

Welcome to WindowBlinds!

You've probably thoughts to yourself over the years "If only Windows wasn't so ugly..." Well, you weren't the only one thinking that. In addition to the standalone version you've just installed, WindowBlinds is part of Stardock Systems Object Desktop for Windows. Be sure to visit our web site at http://www.stardock.com for additional information on components and fully functional evaluation versions of Control Center and IconPackager.

As we continue to enhance WindowBlinds and Object Desktop in the coming months, we look forward to hearing from you about what we can do it help you work more effectively.

Be sure to visit http://www.windowblinds.net, http://www.betanews.com/contest, http://www.skinz.org, and http://www.customize.org to download additional WindowBlinds personalites/skins.

Enjoy!


Personality

WindowBlinds personalities ("skins" is used generically throughout this document to refer to personalities) are installed and loaded from this section of the WindowBlinds configuration options.

To change a skin, simply select it from the listbox and either double-click on it or click Apply Now. This will load the skin and immediately apply it to all open windows on the system (as well as new ones).

Install a new skin from a zip file

After downloading a new skin from a site like http://www.windowblinds.net, press this button to open a file dialog. Using the file dialog, select the .ZIP file you downloaded and press OK to automatically install the downloaded skin from the .ZIP file to your WindowBlinds directory.

Note: WindowBlinds is currently relying on the name of the .ZIP file downloaded to install the skin properly. If the name of the .ZIP file is not the same as the .UIS file inside the .ZIP file, rename the .ZIP to match the .UIS filename. e.g. MyLatestSkin1.ZIP is downloaded, but the name of the .UIS file inside it is MyLatestSkin.UIS. The .ZIP file must be renamed to MyLatestSkin.ZIP in order to install properly.

Delete

Remove the selected skin and its associated files from the computer.

Refresh list

Check the hard drive to rebuild the list of skins displayed.

Apply Now

Load the selected skin and apply its attributes and any settings configured elsewhere in WindowBlinds immediately.

Close

Close the WindowBlinds configuration panel. You can access the configuration panel again by clicking the right mouse button on the WindowBlinds icon in the Windows system tray (next to the clock) and selecting Configure WindowBlinds.

To unload WindowBlinds from memory, click the right mouse button on the WindowBlinds icon in the system tray and select Unload WindowBlinds.

Help

Load the included documentation.


Settings

The Settings tab is used to control how and if WindowBlinds utilizes some skin features. These changes take effect immediately upon pressing Apply Now with the currently selected skin.

Replace standard buttons with bitmaps

Change buttons (like Apply Now and Close in the image above) to the custom buttons (if any) included with the loaded skin. If the skin does not include buttons, WindowBlinds default set of enhanced buttons (from the bms.bmp file in the WindowBlinds installation directory) will be used. [UIS1 and UIS2 skins]

Replace checkboxes & radio buttons with bitmaps

After applying a new skin, graphical checkboxes (like those in the image above) and radio button controls will be replaced with images defined in the current skin (or the WindowBlinds default enhanced images). [UIS1 and UIS2 skins]

Use bitmaps for the taskbar

Use the task.bmp in the WindowBlinds directory or a bitmap specified by a skin author for the buttons on the Windows Taskbar. Note: WindowBlinds does not currently change the display of some portions of the taskbar like the "Quick Launch" area from Internet Explorer 4.0 (or later). [UIS1 and UIS2 skins]

Use the colours recommended by the designer

Use the colors coded by the skin author for active titlebar text, inactive titlebar text, the color of the main menus in applications, and the color of the menu text. Future WindowBlinds releases will include additional control over more aspects of Windows color settings.

Adjust menu borders

If the skin author has included a suitable bitmap, adjust the edges of menus to use their custom image or the default WindowBlinds file.

UIS1 only (these options only apply to UIS1 format skins)

Stretch titlebar bitmaps

Stretch the image used for the titlebar bitmap to fill the titlebar rather than tiling.

Use bitmaps for window borders

Use author-specified images for the borders of windows. Almost all users will want to check this option.

Use Intelligent Fonts

Many applications display the location of the current file in the titlebar in a format along the lines of "MyApp - C:\MyFile.txt". When Use Intelligent Fonts is checked, any text to the right of the "-" in instances like this will be less emphasized in appearence.

Centre titlebar text

Display titlebar text in the center of the titlebar rather than beginning from the left edge.

Right align titlebar text

   Align titlebar text to the right edge of the titlebar.


Backgrounds

The Backgrounds tab is used for changing the bitmap images used as backgrounds in most dialogs, MDI (Multiple Document Interface) applications, and Explorer windows.

Change Bitmap

Select one of the three choices from the display and click Change Bitmap. A file dialog will open in the directory containing the selected image (or the directory of the last image changed). Select a new Windows-formatted bitmap (.bmp) file for use. Please note that only bitmap files are usable. The preview panel on the right side of the file dialog will allow you to preview images before selecting them.

Add bitmaps to dialog / MDI backgrounds

By default, WindowBlinds will attempt to apply a bitmap image to controls using the dialog class as well as the "background" of applications that adhere to the MDI model (basically any application where you have multiple open files inside one overall window).

Add bitmaps to Explorer windows

WindowBlinds includes support for applying a background image to all your Explorer folders both in regular modes and when you are using the View as Web Page options of Internet Explorer 4.0 (or later).

Stretch to fit

Rather than tile an image smaller than size of Explorer folders, WindowBlinds will stretch it to fill the entire window.

Show Inactive State

Use a different image for the background of Explorer folders when they are not the active (highlighted) window. Selecting this option adds another visual element to WindowBlinds, but is marginally slower as an additional bitmap must be used.

Transparency

You've seen the screenshots, you've drooled on your keyboard, and now you too can have semi-transparent Explorer folders. Semi-transparent? That's right, at the moment, Explorer folders are only transparent down to the desktop background bitmap (other windows in the z-order beneath transparent Explorer folders will not be visible).

Remember, your computer and video card are going to be pushing around a lot of pixels if you enable this option, so it will be a bit slower in moving windows. You may want to disable full-window drag to speed things up a bit.

Occasionally, you may need to restart WB and/or your computer to get this feature working. If it is not working right off the bat, ensure Use Explorer Bitmaps is checked and Stretch to Fit is not.  The left panel of the IE4 "Web View" will not be effected at the moment. If you are having problems, try updating your video drivers to the latest available from the manufacturer of your video card. Some laptop chipsets in particular seem to be really unhappy with this feature. Needless to say, we are still working the kinks out.

See the Tips and Tricks section of this document for some additional information on this transparency support and ways to manipulate its look.

Note: settings for dialog/MDI/Explorer bitmaps are definable by individual skin authors, so the images previewed on this tab are not necessarily the images that will be used with all skins. Add bitmaps to Explorer windows must be enabled and Stretch to fit must not be enabled with WindowBlinds to allow the semi-transparent Explorer folders to function (see Tips and Tricks).


System

The System tab can be used to enable/disable optional global WindowBlinds features that are in effect regardless of the skin currently loaded.

Replace 3D toolbars with flat ones

Change application toolbars to have the "flat" look popularized by applications like Internet Explorer 4.0.

Smoothly scroll instead of jumping up / down pages (disabled in this build)

Changes how small the "steps" are when scrolling in Explorer folders.

Ignore 16-bit applications (disabled in this build)

[locked] WindowBlinds currently ignores all 16-bit applications running on the system and does not attempt to change their behaviour.

Make desktop icon text background transparent

The area behind an icon's text on the desktop is normally set to the same color as the Desktop background color definition in the current Windows scheme settings (see Control Panel -> Display -> Appearence to alter these). This option removes the color from behind the text and makes the background transparent so the Desktop is not obscured.

Make maximized windows show the borders

Checking this option ensures that the borders of maximized windows will not "spill" over the edge of the desktop. On skins with very thick window borders, portions of the borders appear offscreen for maximized windows unless this option is checked.

Use bitmap backgrounds specified in UIS file

Use the bitmaps defined by skin authors for dialog/MDI/Explorer backgrounds as opposed to the defaults setup in WindowBlinds. See Backgrounds for configuring the WindowBlinds default background bitmaps.

Make windows stick to screen borders

Enabling this option will prevent any portion of a window from being moved past the "edge" of the desktop.

Show this dialog when WindowBlinds starts

Enable this option to display the WindowBlinds configuration window when WindowBlinds is started.

Remember, you can also start WindowBlinds and adjust its configuration through the WindowBlinds applet in the Control Panel (under your Start Menu).

Put icon in the system tray for easy access

Display a WindowBlinds icon in the system tray (next to the clock). Click the right mouse button on this icon for convenient access to configuring and unloading WindowBlinds, as well as this help file.

Run WindowBlinds automatically on startup

Creates a RUN entry in your Windows registry to automatically load WindowBlinds each time you start Windows. Loading WindowBlinds from the registry on startup results in the system displaying a dialog on load that enables you to not load WindowBlinds on startup (if you desire).

Note: changes to most of these settings will not take effect until the next time you start WindowBlinds.


Exclusions

Per App

Application specific skins

WindowBlinds allows you to configure different skins for use with different applications running at the same time.

Set a Per App skin

Selecting Set a Per App Skin will bring up a standard Windows file dialog. Navigate to the directory containing the application you would like to have a specific skin (check its shortcut properties if you are unsure exactly where it is located) and select the appropriate .EXE file

The location of the .EXE file makes no difference, so if you happen to know the .EXE name, you can simply enter it into the file dialog directly and select OK.

An additional dialog (not shown above) will appear with a listing of the currently installed skins (based at the moment on their directory names, not the descriptive names seen on the Personality tab). Select the desired skin for use with this application here and select OK.

The Per App skin will take effect the next time you start WindowBlinds.

Remove Per App setting

Remove the selected Per App setting.

Exclusions

Exclusions are a tricky business when it comes to WindowBlinds. While it would be wonderful to have 100% of Windows applications on 100% of the systems working 100% of the time, this is unrealistic. Even Windows itself is not 100% happy on 100% of machines out there. Programs which handle their own drawing routines, use custom controls to function, or a myriad of other things can become unhappy when WindowBlinds attempts to work with them. Some programs, like the disk defragmenter in Windows 95/98 and the Task Manager in Windows NT have been hardcoded as exclusions because, in all honesty, they are "critical" enough that nothing should ever be messing with them.

We have had to "play it safe" when it comes to adding applications to the exclusion list. While some applications uniformly refuse to cooperate with WindowBlinds on any system, it is quite possible that an application excluded above may work fine on your system. If you find your "favorite/gotta have it" application is not being effected by WindowBlinds, try removing it from the exclusion list and restarting WindowBlinds.

Some applications are "excluded" in specific ways (like preventing WindowBlinds from changing their menus) to work around potential problems. A few programs, such as RUNDLL32.EXE which loads Control Panel applets, are hardcoded as exclusions at the moment to prevent the possibility of odd behavior with important system functions. As WindowBlinds continues its development, we hope to reduce the number of applications excluded by default as much as possible.

Add Application Exclusion

Selecting Add Application Exclusion will bring up a standard Windows file dialog. Navigate to the directory containing the application you would like to exclude (check its shortcut properties if you are unsure exactly where it is located) and select the .EXE file to exclude.

The location of the .EXE file makes no difference, so if you happen to know the .EXE name, you can simply enter it into the file dialog directly and select OK.

Remove Exclusion

Delete the selected exclusion.


Support

With hundreds of millions of 32-bit Windows machines (and more all the time), tens of thousands of applications, hundreds of peripherals, and all sorts of other variables in the mix, statistically WindowBlinds will probably get confused at times.

There are a vast variety of applications out there from thousands of developers. Some follow Windows programming guidelines better than others, which is important with WindowBlinds because hidden little problems that might not otherwise be visible tend to creep out when WindowBlinds is working its magic. If you are having problems with a specific application, please try adding it to the exclusion list.

Getting in touch with Stardock

Should you find a bug or have additional comments, please get in touch with Stardock Systems so that we can help resolve them.

The best place for bug reports/suggestions/general chat is the WindowBlinds newsgroup.

Server : news.stardock.com

Group : stardock.windowblinds

URL: news://news.stardock.com/stardock.windowblinds

We are also found in the #stardock channel on EFNET and you can e-mail us at wblinds@stardock.com.

Information on new releases, FAQ's, and additional downloadable personalities/skins can be found on the Stardock Systems web site at http://www.stardock.com or at http://www.windowblinds.net.

Lost Registration Information

While we suggest printing a copy of your registration information, should you happen to lose it you can visit http://www.stardock.com/products/windowblinds/faq.html for a link to check your serial number.

I thought WindowBlinds was freely available, what's up with the registration dialog?

WindowBlinds is part of Stardock's Object Desktop for Windows (http://www.stardock.com/products/odnt/) in addition to being available for registration as a standalone product. Registrations for pre-1.0 WindowBlinds versions will be good for 1.x versions (you won't have to upgrade after the beta). As we move toward WindowBlinds 1.0, we are experimenting with different registration approaches. As long as a percentage of users register, WindowBlinds will continue to be freely available and uncrippled. After ordering online via Stardock's Secure Commerce Server, you'll receive an email (generally within 10 minutes) with your registration key.

Object Desktop users should download and install WindowBlinds from the Component Manager servers, as that version will automatically register itself on installation.

Why doesn't WindowBlinds do scrollbars/progress bars/etc.

One thing at a time. We've been working very hard on improving the stability and performance of the WindowBlinds base engine. Features are being added as we go. We've got lots of cool stuff in store...

Known Issues (some of them actual problems, some just things to be aware of)

- Application X is not getting any WindowBlinds effects

Some applications are excluded by default either in the exclusion list or hardcoded into WindowBlinds. We have erred on the side of caution if there is the possibility of a problem. Feel free to try experimenting with removing some of the exclusions. For instance, Telnet

is excluded by default but it is really on needed as an exclusion on Windows 95 (we've yet to fix a bug with respect to it resizing itself).

- This skin is cutting off part of my application's window

Though this tends to happen with skins with very large window borders, it can also show up in some other instances (like the Calculator applet included with Windows). Some of these windows are not properly reporting their size and are thus a little problematic at the moment. We are working on this, but forcing non-sizeable windows to resize is a tricky business.

- I downloaded a skin and installed it, but it's not showing up in the list

WindowBlinds is currently relying on the name of the .ZIP file downloaded to install the skin properly. If the name of the .ZIP file is not the same as the .UIS file inside the .ZIP file, rename the .ZIP to match the .UIS filename. e.g. MyLatestSkin1.ZIP is downloaded, but the name of the .UIS file inside it is MyLatestSkin.UIS. The .ZIP file must be renamed to MyLatestSkin.ZIP in order to install properly.

- Application X is crashing, help!

If a particular application has problems when WindowBlinds is loaded, try adding the .EXE for that program to the WindowBlinds exclusion list. We've included several programs in the default exclusion list that are known to currently cause problems for some users (and we'll continue to try and work around these problems in future releases).

- WinAmp or kjfol plugins are crashing when run with WindowBlinds

WinAmp plugins should be coexisting happily with WindowBlinds now, but there is a known problem with one of the default plugins supplied with the kjfol MP3 player. The plugin does not pass messages appropriately to the system and this tends to "confuse" WindowBlinds and cause it to stop skinning applications.

- Unloading WindowBlinds

Unloading WindowBlinds should function properly and not cause any running applications to crash. If this is not working correctly, please contact us so that we can fix any remaining problems.

Should WindowBlinds be crashing on unloading, try closing open applications beforehand. Alternatively, apply the "disabled" option on the WindowBlindsconfiguration page to remove the enhanced effects.

- The text in my dialogs on Windows 98 is all screwed up!

Some video card drivers do not properly implement some features at all resolutions and color depths. Odds are, based on our testing, any RIVA-based video board running in 16-bit color under Windows 98 will exhibit this problem (not all of them, but enough). Simply switch to 32-bit color mode and you should be all set. The Trident 9xxxx series also appears to be problematic on some systems.

- Internet Explorer folders are no longer getting WindowBlinds effects

Sometimes, Internet Explorer folders get a little confused and no longer show the WindowBlinds effects. Reboot and you should be all set.

- Using Custom Buttons

Custom buttons using UIS2 skins may appear to be slightly clipped on the right edge, particularly on Windows 98. This is due to a bug in the StretchBLT call that we have not yet worked around. Disable custom buttons on the Settings tab if desired.

- Explorer crashes

These may still happen from time to time. If they are reproducible, please let use know what is causing them to happen on your system.

You might also try disabling the bitmap support for dialogs and Explorer backgrounds.

- WindowBlinds crashes when I start it (possibly Explorer as well)

Make sure your video drivers are updated to the most recent level.

Try closing all running applications prior to starting WindowBlinds and adding them back in one at a time to find what is conflicting.

- MSDOS prompts and Word MDI child windows look like they always do

These windows are somewhat naughty in their implementation. WindowBlinds does not support changing them (this will probably change in the future for Word).

- Menu's and their flyout menu components have a gap between them

This only happens with a few skins, but it's a WindowBlinds bug. We're working on it.

- What's up with 16-bit applications?

By default, all 16-bit applications are excluded from being impacted by WindowBlinds. Some 16-bit apps do work fine with WindowBlinds, so feel free to 	experiment with	disabling this option.

- There is a crash in EM_EXEC when starting WindowBlinds

We are working on a conflict between some levels of Logitech software and WindowBlinds. This does not occur on all systems, so its taking some time. Loading the Logitech software after WindowBlinds should [re]enable all functionality.

Updating your Logitech drivers to the latest revision available from http://www.logitech.com also appears to help in many cases (as opposed to the driver included with Windows).

- My Explorer folders are gray after unloading WindowBlinds

This is a side effect of unloading and releasing the folder background bitmap from memory. Any open folders will have their correct colors the next time you open them.

- Yikes, this personality looks really bad on my system!

We are still enhancing the UIS2 format so that skin authors can define suitable system colors for a particular personality.

- This personality looks SO COOL!!!

Most personality authors include their email address in the UIS file or in a README file in the ZIP it is distributed in. Consider sending them a short note to thank them for their efforts.

I'm not interested, I want it off my system!

Well, we're certainly sorry to hear that and we hope you'll check out future WindowBlinds releases down the road. Simply use Add/Remove Programs (in your Control Panel) to uninstall WindowBlinds. If you have configured WindowBlinds to start from the registry, please disable this option prior to uninstalling. We also recommend that you reboot without WindowBlinds before uninstalling to make sure the files are removed.

If you have added additional skins, you'll need to delete the \Program Files\Stardock\WindowBlinds directory to remove them. We've played it safe with the uninstall and not attempted to remove additional files.


Tips and Tricks

This section is a bit sparse at the moment, as we have deactivated and/or hidden several "cool" features until further along in the development process to concentrate on the stability and performance of the core engine.

More skins! I want more!

There are more new ones all the time, with plenty to go around. And you can always design your own (see the Creating a Skin tab).

The best sources for skins are http://www.windowblinds.net, http://www.betanews.com/contest, and http://www.skinz.org. http://www.customize.org is also an excellent source for all your application skinning needs.

Suppress the configuration dialog on startup

Rather than loading WindowBlinds from the registry (see the System tab), create a shortcut icon in your Startup folder with a target of:

"C:\Program Files\Stardock\WindowBlinds\wbload.exe" quiet

It is necessary to place the quiet parameter outside of the quotes around the wbload.exe location.

Enable transparent Explorer folders

You've seen the screenshots, you've drooled on your keyboard, and now you too can have semi-transparent Explorer folders. Semi-transparent? That's right, at the moment, Explorer folders are only transparent down to the desktop background bitmap (other windows in the z-order beneath transparent Explorer folders will not be visible).

Remember, your computer and video card are going to be pushing around a lot of pixels if you enable this support, so it will be a bit slower in moving windows. You may want to disable full-window drag (via the Plus! tab on Windows NT or another application like IconPackager) to speed things up a bit.

Simply enable the Transparency option on the Backgrounds tab in the WindowBlinds configuration window and press Apply Now. You may need to restart WB and/or your computer to get it going. If it is not working right off the bat, ensure Use Explorer Bitmaps is checked and Stretch to Fit is _not_.  The left panel of the IE4 "Web View" will not be effected at the moment. If you are having problems, try updating your video drivers to the latest available from your manupdating your video drivers.  Some laptop chipsets in particular seem to be really unhappy with this feature. Needless to say, we are still working the kinks out.

Changing the tint on transparent Explorer folders

This change requires editing the registry. Do not do this if you are not comfortable editing the registry. Add a new string value named "transBCOL" without the quotes under the key HKEY_CURRENT_USER\Software\Stardock\WindowBlinds\wb5.ini\WBLiteFX .

The colors are:

0=Default Blue

1=Yellow

2=Pink

3=Red

4=Green

5=Blue

6=Green (again)

7=Clear

You can attempt to experiment with other values, but the above appear to work nicely in most instance.

Improving the performance of Explorer folders

On the Backgrounds tab, ensure that Use active and inactive images is disabled. This forces WindowBlinds to use only one image from the backgrounds of Explorer folders.

Alpha blending for buttons and titlebar plugins

See the index.html file in the WindowBlinds directory (the UIS2 File Format document under the WindowBlinds folder in the Start Menu) for information on utilizing WindowBlinds support for real-time alpha blending and effects. This requires creating or modifying an existing skin.

Titlebar Animation

Don't forget to check out the information in the index.html file in the WindowBlinds directory for instructions on constructing skins with animation in the titlebar!


About

WindowBlinds 0.90

Part of Object Desktop for Windows

http://www.stardock.com/products/odnt

If you like WindowBlinds, be sure to checkout IconPackager, Control Center, Object DriveScan, Netscan, and all the other components of Object Desktop for Windows!

IconPackager is the perfect complement to WindowBlinds (and it includes a boatload of additional features for tweaking your system's shell). It can downloaded from http://www.stardock.com/products/iconpackager/.

An OCX demonstation version of WindowBlinds for use by developers in their applications is available for download from http://www.windowblinds.net.

Special thanks go out to all the people who have sent us feedback and suggestions.

Stardock Systems

17292 Farmington Road

Livonia MI 48152

Phone: 734-762-0687

Fax: 734-762-0690

WWW: http://www.stardock.com

Sales: sales@stardock.com

Support: support@stardock.com

Copyright 1997-1999 Neil Banfield and 1998-1999 Stardock Systems, Inc.

WindowBlinds is a trademark of Stardock Systems, Inc.


Order
WindowBlinds Registration

WindowBlinds is available as a stand alone product as well as one of the many components in Object Desktop for Windows Network Edition. WindowBlinds stand alone is $19.95. Object Desktop for Windows is $49.95.

If you order WindowBlinds stand alone, your registration number will be effective for all WindowBlinds 1.x versions.

Visit http://www.stardock.com/products/odnt to learn more about Object Desktop for Windows Network Edition.

You can register WindowBlinds in one of three ways:

(1) On-line Registration.

(2) Order by phone by calling: 1-800-672-2338

(3) Standard mail registration.

* On-line Registration *

Visit http://www.stardock.com/stardock/estore.html which is the home of our secure commerce server. From there you can enter your Visa or Mastercard credit card number. The secure commerce server will validate your card and create a registration number for you to enter into WindowBlinds.

* Standard mail registration *

Fill out the order form below (include Visa/Mastercard information or a check/money

order drawn on US dollars) and send it to:

Stardock Systems, Inc.

17292 Farmington Rd.

Livonia, MI 48152

Phone:(734) 762-0687

Fax: (734) 762-0690

WWW: http://www.stardock.com

------- cut here --------

Choose 1 of the following:

[  ] $19.95 WindowBlinds stand alone registration.

[  ] $49.95 Object Desktop for Windows (Network Edition)

________________________________________________________________

Name

________________________________________________________________

E-mail address

________________________________________________________________

Address

________________________________________________________________

Address and phone number

________________________________________________________________

City/State/Zip/Country

________________________________________________________________

Credit Card Number / Expiration Date

[Checks/money orders for US dollars are also accepted]

________________________________________________________________

Signature (for credit card orders)

WindowBlinds is a trademark of Stardock Systems, Inc.

------- cut here --------


Skin Creation


Skin Creation
Creating a Skin

Believe it or not, it's relatively simple to create your own custom personalities for WindowBlinds. In their most basic form, a personality consists of a text file defining the location of bitmaps and functions for the skin and its buttons.

Under the WindowBlinds folder in your Start Menu is a UIS2 File Format link (which points to the index.html file in your WindowBlinds directory) that contains information on all the supported functions of the .UIS (User Interface Scheme) file format.

Also look at how your favorite skins are put together to see how they work their magic.

Also on the Downloads page on http://www.windowblinds.net is a UIS2 Plugin SDK that programmers can use to create custom effects. It's currently setup for use with Microsoft Visual Studio. A UIS2PLUG.ZIP file containing the latest version of this SDK is in the WindowBlinds directory of your hard drive as well.

Keep those great skins coming!