[+][SUG][PL] Clear Physics: Abolish color cycling, pick good non-clashing colors

[Simon]

I would like to learn Proxima's reason for why he prefers darker lemmings. I know that lemmings at (0x80, 0x80, 0xFF) become similarly light as the earth (some light grey). Is the lemming-to-earth contrast your reason?

When I know more, I can start recommending better defaults for the CPM color config file.

The meaning of the bool option is: Ignore what's configured in the dedicated CPM options file, and use this prefixed configuration that you can't choose by editing that file. That leads to the idea: Ditch the option and instead make "cycling" a keyword that can appear directly in the CPM color config file. After all, the behavior is either-or, and now the way to configure it will be clearly either-or, too, not a product of 1. bool, 2. color. You can print comments into the file to explain "cycling".

If you keep the bool option nonetheless, consider to default it to no color-cycling. Reason: That's most helpful for new users who won't look into the options. WillLem can then activate the option for his cycling.

I still think that the CPM color config file should go into user/.

Should I make 3 fresh topics for these 3 sub-issues (default colors, how to choose cycling, location of the config file)?

-- Simon

[WillLem]

Ditch the option and instead make "cycling" a keyword that can appear directly in the CPM color config file ... You can print comments into the file to explain "cycling".

This is a good idea. The bool option does seem a bit wonky as it's unclear exactly what will cycle when the option is on.

Should all elements be allowed to cycle (Gadgets, Lemmings, Triggers, etc)?

If you keep the bool option nonetheless, consider to default it to no color-cycling.

OK, if we keep the option let's toggle it off by default. I probably prefer your idea of keeping all CPM color concerns to the .nxmi though; let's focus on that going forward.

I still think that the CPM color config file should go into user/.

Agreed, this does make the most sense.

Should I make 3 fresh topics for these 3 sub-issues (default colors, how to choose cycling, location of the config file)?

No need, this topic is sufficient for all concerns. I've downgraded the status of this topic from

Code Select Expand

[✓] (resolved) to

Code Select Expand

[+] (in progress).

[Simon]

Should all elements be allowed to cycle (Gadgets, Lemmings, Triggers, etc)?

I wager that this cycling is mainly for yourself.

If I were to implement it, I might allow it purely because the alternative would be to special-case something (gadgets would be special). I like to avoid that. Implementing it saves a user-visible explanation, even if it's only "for gadgets, you can also put" instead of "you can also put" in the comment in the config file. If we don't make it clear, we'll eventually get a bug report.

On the other hand, I don't need it, and if you don't need it, chances are that nobody needs it. Do what makes yourself feel best. I don't know how it looks in the code. If it's nasty in the code ...

-- Simon