Previous Next Table of Contents

3. Icons, graphics and pixmaps

3.1 Icons staying put

When I click on some of the icons they fan out and stay there until I restart Wharf. What's the deal?

In old versions of AfterStep, an icon to be used in Wharf must contain at least one transparent pixel, otherwise the symptoms you've mentioned will be prevalent. Simply add a transparent pixel and everything should work flawlessly (see question transparent_icons for instructions on how to do this).

Newer versions of AfterStep fix this problem, allowing you to use icons without transparent pixels in the Wharf without problems. You should really upgrade to the latest version.

3.2 Colormap issues

When I run AfterStep some of the icons on the button bar don't show up. If I load them at the top they show up, but then the other ones don't. Also, when I use netscape, the colors get wacky. What's wrong?

Odds are you are using a 256 color (8bit) display. A quick explanation is that you can only have 256 colors on the screen at the same time, and the more colors you use in Wharf (the button bar), the less you can use for other applications and icons. I would suggest upgrading your video hardware or using more conservative (less colorful) icons. For netscape, an option is to run it with the netscape -install` command. This will insure that netscape gets a good deal of the color that it wants. However, this will result in the colors flashing whenever you move the mouse in or out the Netscape window. You decide if you can live with that.

You can find some help on configuring AfterStep for running on an 8-bit display in http://www.infinet.com/~gnosis/as.html. You can find a good collection of low-color icons (all of them together use only 21 colors) at http://www.iis.ee.ethz.ch/~kiwi/AfterStep/.

If you are using asclock, you can configure it to use much fewer colors. See question asclock_few_colors.

3.3 Icons disappear from Wharf. What's wrong?

You are most likely running out of colors. Either upgrade your hardware, switch to a higher color depth (i.e. 16 bpp or higher), or use icons that contain fewer colors. See question colormap.

3.4 How do I create an icon with a transparent pixel?

Its beyond easy. An xpm is a simple text file. Therefore, the only image manipulation software you will need is vi. If you edit your xpm, you will become aware of the beauty and simplicity. At the bottom you will notice a character representation of your image. At the top there is a color listing corresponding to each pixel of the character representation.

You have two options to create a transparent pixel:

Change an existing pixel color to transparent:

Simply find the pixel character(s) you wish to become transparent, then go back up top and find that character in the listing. Change the color code (number beginning with a #) to None. Save, and you're all tootin'.

Create a new transparent pixel:

Edit the line near the top corresponding to the height/width/number of colors/chars per pixel. Increment the number of colors (third value) by one. Then in the list of pixels and color values add the line:

     "c None",

Where `c' should be a character that is not being used by any other color. From there save and take off.

If you're the slightest bit unsure, take a look at one of the xpm files in the AfterStep distribution's icons directory.

The `correct' size for a Wharf icon is 48x48 pixels. However, if you use bigger icons, they will display correctly, up to 64x64, which is the default size for the Wharf buttons.

3.5 Why doesn't program `xyz' work in 16bpp?

A lot of 8bpp programs don't work on displays without a PseudoColor visual available. A lot of PC X servers don't support PseudoColor visuals on displays running in TrueColor mode. You should buy an SGI. Or run two simultaneous X servers, if you're on Linux.

3.6 Why doesn't xv do `xyz' in 16bpp?

xv doesn't cope well with 16bpp in three ways. First, it can't grab pieces of the screen. Second, if you grab pieces of the screen with xwd and try to display them with xv, it doesn't work well. xwud works. Third, if you display a 24bpp picture, it doesn't bother to dither it down to 16bpp, resulting in bad pictures.

3.7 Why don't icon names change when the application changes it?

I have some application creating a window and then changing its name to something special. I have told AfterStep to give the special window name a special icon. But I never see the icon. Why doesn't this work?

AfterStep assigns icons to windows when they are created, not when they are iconified, and later title or icon-name changes don't cause the icon to change. Perhaps this is a bug.

Emanuele Caratti ( wiz@iol.it) has created a patch that supposedly fixes this, but I have not tried it, and it's not (yet) part of the official distribution. You can find it at ftp://afterstep.foo.net/pub/AfterStep/mods/dynamic_icons.tar.gz.

3.8 Suddenly, some windows stay always on top. Why?

Sometimes, after I've been using AfterStep for some time, certain application windows stay always on top; they even stay on top of the Wharf and their own dialog boxes!

With the default .steprc, triple-clicking on a window titlebar toggles a window's always-on-top state. Triple-click again to remove it. If you want to remove this feature, locate the lines in your .steprc that look like this (there are several of them):

        PutOnTop        "TripleClick"

and delete them. Or better yet, just comment them out, in case you later decide you need the feature again.

3.9 Can you add `xyz' to the Wharf?

You know, it would be really nice if the Wharf supported text titles/cascading menus/tabs on the side/plug-in modules/swallowing running applications in folders/scrollbars on folders/starting applications only if they're not already running. Why doesn't someone do it?

This is a holy war. You will be crucified at dawn. Unless you implement it yourself and post a patch.

No, seriously, there has been a lot of discussion about these topics. Many people believe that AfterStep should be kept as close as possible to the original NEXTSTEP interface, why others think it should be extended and be made as configurable as possible. Most probably the appropriate thing is some point in between, but then again, that is a personal issue. For now, we will let the developers decide the direction AfterStep should take.


Previous Next Table of Contents