This is a very minor annoyance, but I think it might be worth bringing up. Since Rhino 6 was introduced, the brown colour in the standard colours looks more like red to me. Is it just me? Does anyone else see an actual shade of brown?
I know how to change the colours, and I’ve been doing it for quite a while now, but every service release has reset this colour. I was hoping in Rhino 7 that either the colour would actually be brown, or the file that controls the colours would not be overwritten with every update. But it’s still the same. With over 130 users it’s not practical to keep re-copying the colour configuration file every month when a SR is released.
Hi Dan - it’s always been more red than brown to my eye. Does rgb 147 91 79 look better? If so, or even if not, (pending any change here) you can change it in
Give me a nice brown rgb that you like and I’ll put it on the pile to tune up. I don’t want this question Is brown really brown?
to keep me up nights, now that is has been asked.
You know my preference.
The HSV sliders put the default Brown rgb ,191,63,63 definitely in the red camp. Whereas the Browns are over among the oranges, hue wise. I think we can tune this up…
Interesting that in that set, ‘Brown’ is back at red - like what we have now, that everyone (here) finds…annoying. ‘Saddle Brown’ though has the same hue as our ‘other’ browns.
You’re right, though, we’ll probably get flack too, if we make it too non-standard.
Why not leaving the color and changing the name from Brown to Dark Red? We already have Green / DarkGreen, and Blue / Dark Blue. Having Dark Red would help to organize stuff by base colors.
Right but, orange, not red… it is just plain weird to call #A52A2A ‘brown’, especially if all the other browns in our list are orange.
Jess’s way may be a good way out - hmm - except ‘dark red’ exists in that W3C list… or simply putting ‘Saddle Brown’ in the list where Brown is now, and relegating that red version of brown to an un-named place among all the other reds further down the list. That way we won’t break any naming conventions.
