This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
> When a user creates a new display (say contours), its display label is set > to a random color. > > That color doesn't correspond to any aspect of the display (the color of the > contours etc.), > so it is just arbitrary. It is meaningless at best, and often enough happens > to come out > actively confusing (the green display label refers to the mostly red contours > while > the red display label means the mostly green contours or whatever). > > Yes, every user could be trained to know enough to burrow down > 2 menu layers and change the display label color, every time. > But why should they have to? It is needless "data friction." > > My suggestion: if my color scheme is "white on black", or "blue on white" > then why not have all display labels default to white or blue respectively? Brian, This make sense to me too. We can discuss this in our next committee meeting. Yuan > > Then if label color is added by the user, it is to give it value and meaning, > instead of having meaningless use of color that almost requires you to change > it. > > Thank you, > Brian > > > > Ticket Details =================== Ticket ID: KNR-996514 Department: Support IDV Priority: High Status: Closed