Well, it might be most useful to have the 'other color' state initially reflect what the colors are in the original hilighted text. Also, in the same vain, an option for, "Match only if the same color as hilighted.', might be nice, since you may only want it to match in specific blocks of text that have a certain predetermined color. Selecting the option would show two more color selectors, which also default to the 'current' color of the word you hilighted. Then you could change it if, for example, the text you hilighted was in one color, but you wanted to look for it in a room, which is a different one. In this case though, the options need to allow for the existing ansi colors as named items you can pick in the color picker for it. While the custom colors are useful, they may not reflect the 'real' colors you are looking for from the mud.
And on a similar note. It might be useful to allow people to give a new color they create in the color picker a name, which would appear in the existing list of color names. That way you can more easilly select it later, instead of having to remember what settings you used or using an existing one. Of course you would only want them to override their own colors in those case, not the default set. If you want brown that looks brown, instead of reddish, you can just call it "TrueBrown" and pick that when you want it, rather than replacing the predefined ones, etc. However, I would suggest that this option be limited to the main world and not script accessible, since you don't want someone's plugin overriding the color table in the main world, or the even greater confusion of 5 plugins, all with a different definition for "My_Green", none of which match the "My_Green" from the main world file... lol |