A consequence of getting the incremental-refresh logic right.
> - Thanks for dark blue! The cyan was barely readable. Now all the colours
> are nicely readable. I don't necessarily like your choice of colours but as
> long as I can read the text, that's fine.
It's a difficult balancing act. A lot of the people asking for color changes
aren't aware of some of the constraints -- one of them being that 12% of the
male population has red-green color blindness. Blue turns out to be about the
only color that people with any form of color blindness can recognize.
> - When I set something to yes it goes green. When I then set something else
> to yes the new one goes green, too, but the old one also remains green. Is
> this intended? (i.e. does green mean "already visited" or something like
> that?) Also, on the CPU selection menu, it started off with two of the CPUs
> already in green (but only one with a yes). Is that a feature or a bug?
That's right. Green means "visited or set".
> - Moving left/right can still be quite painfully slow...
I know. The basic problem here is that the configurator has to recalculate
visibilities for every item in the new nenu. I have some ideas for speed-
tuning this.
> - Setting options is sometimes very slow, sometimes ok... (depends on
> complexity of underlying rules I guess)
Yes. There is at least one more major speedup I may be able to get out
of this.
-- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>Whether the authorities be invaders or merely local tyrants, the effect of such [gun control] laws is to place the individual at the mercy of the state, unable to resist. -- Robert Anson Heinlein, 1949 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/