Re: Feature Request: Recommended Cable Colors
Posted: Thu Jul 01, 2021 3:14 pm
I don't want this discussion to go around in circles generating heat but no light.
We all agree that users should be able to assign whatever color they want to individual cables using the existing mechanism.
This would always override any default choice of color.
What I'm suggesting is that users are offered the option to go further than that if they want to enjoy automated cable coloring.
I personally don't care what the actual colors are, what I care about is ease of use and consistency.
So I'd be very happy with a standardized/standardised color/colour scheme that was used if users engaged the RECOMMENDED button. They would still be able to override colors on a cable by cable basic or simply not engage the button and have the existing setup.
But I accept that many people are not prepared to adopt standardization. I don't understand why as the benefits would be enormous but there you go.
So the next, more complex and less standardized mechanism is to use what I described earlier as a logical coloring system where you can assign your own colors by function. It's more complicated and harder to implement and it would still be confusing when patches are shared as nobody would know what the colors meant but at least we could enjoy automation and internal consistency.
BUT you'd still have default assignments for those logical colors wouldn't you?
So before you made gate signals your preferred color they would be assigned to a default color, right?
Or would any kind of default standardization be so objectionable that you'd want all logical colors to be assigned to the same color, so that color standardization didn't creep in by the back door with many people not being too fussed about what the specifc colors were and leaving the logical colors with their default assignments? Which would lead to a de facto standard wouldn't it?
We all agree that users should be able to assign whatever color they want to individual cables using the existing mechanism.
This would always override any default choice of color.
What I'm suggesting is that users are offered the option to go further than that if they want to enjoy automated cable coloring.
I personally don't care what the actual colors are, what I care about is ease of use and consistency.
So I'd be very happy with a standardized/standardised color/colour scheme that was used if users engaged the RECOMMENDED button. They would still be able to override colors on a cable by cable basic or simply not engage the button and have the existing setup.
But I accept that many people are not prepared to adopt standardization. I don't understand why as the benefits would be enormous but there you go.
So the next, more complex and less standardized mechanism is to use what I described earlier as a logical coloring system where you can assign your own colors by function. It's more complicated and harder to implement and it would still be confusing when patches are shared as nobody would know what the colors meant but at least we could enjoy automation and internal consistency.
BUT you'd still have default assignments for those logical colors wouldn't you?
So before you made gate signals your preferred color they would be assigned to a default color, right?
Or would any kind of default standardization be so objectionable that you'd want all logical colors to be assigned to the same color, so that color standardization didn't creep in by the back door with many people not being too fussed about what the specifc colors were and leaving the logical colors with their default assignments? Which would lead to a de facto standard wouldn't it?