Hi all, I couldn't stand the ugliness of the border-color code. This computes properly a border that is an average of your focussed and normal border colors, averaged in rgb space. I'm not sure about the best default weighting of this average, but am sure that this is the nicest default behavior: you can see which way navigation will take you, but you don't have to configure yet another color, and it automatically matches with whatever you've already got in your config. Perhaps we could do something analogous for tab colors? Users probably usually only want to configure the background and foreground colors and maybe the contrast? Right now, we've got six colors, and if you change one, you probably want to change three, which suggests they aren't as orthogonal as they could be. David Sat Oct 13 05:05:24 EDT 2007 Andrea Rossato * WindowNavigation: don't export the config constructor and some haddock fixes I told to David I would have taken care of that: instead of exporting the config constructor we export 2 functions: navigateColor and noNavigateBorders. Updated documentation accordingly. Mon Oct 15 12:55:04 EDT 2007 David Roundy * compute a reasonable navigation color based on focussed color. Tue Oct 16 17:03:49 EDT 2007 David Roundy * fix docs on WindowNavigation. Tue Oct 16 17:33:16 EDT 2007 David Roundy * compute nice window border for WindowNavigation properly.