Custom colors & defaults. (3.20)

Will try this later with 3.22, but for the moment:

I set colors. I saved them as a file. I set that as the default.

Then, I go and change one of the custom colors. After changing that, I hit 'override with defaults' for the colors.

Now, I use that custom color for my local echo. I enter a command. It's entered in the changed color, not the one I originally had. Not ideal; the saved colors ought to save more than just ANSI, in my mind.

But, more importantly, when it's set to override, you can't /change/ the custom colors. They lock the same as the ANSI. That doesn't make sense; it should only lock if it's actually loading colors for use in those slots, which it obviously isn't.

This problem still exists, for me anyway, in 3.24. Can someone else verify, please?

The problem is that in the current version(s) you either override all colours with the default or none.

Now that we have XML files (and "include" files) I am planning that in the near future you can override on a colour-by-colour basis, which is what you want. Soon.

I'm fine with it overriding all colors. That's what I want it to do. The thing is that the custom colors /do not/ override with the saved versions, but /are/ locked against any changes, when the box is checked.

OK - I've tested this a bit. It works for me but perhaps in a non-intuitive way. ;)

First, the default colours (and triggers etc.) are only processed when the world is loaded (except for manual intervention, see below).

Thus, if you change colours but then check "override with default colours" this will not take immediate effect, but will affect you next time the world is loaded.

Anyway, what you can do is, after changing the defaults, use the File menu -> Reload Defaults (Ctrl+Alt+R), which forces defaults to be reloaded.

In my testing, the custom colours were also overridden - can you confirm that you think that is not happening? (after doing a "reload defaults"?).

That does fix it. Terrific. :)