That’s actually a Toolbar that for some reason has every button on it hidden - that’s not how it looks by default. Anyway, if you click the gear button in the lower right corner you can select which buttons to display.
It should show you your Project Colors pallet to select from (mine is very customized so it won’t look like yours). You can setup your colors in Project>Project Colors Setup… if needed. Also when Coloring a Track make sure that no Parts or Events are select because it will color those instead of the Track.
Make sure that the track you want to change the color of is selected, and nothing else (i.e. no part(s) are selected). You can do that by first clicking on the track, and then in an empty area of the project window. Then, click on that button that says, “Select Color For Selected tracks or events”, and a list of color should show up, just pick one of those and that should do it. The Project Colors Setup dialog is just if you want to change the default colors.
Yes I understand. But since your toolbar had no buttons it seemed possible your color pallet had no colors, and that is where you’d set them up - hence “if needed” The area you show you want to change can’t be changed. Changing the Track Color changes the part on the left.
So, if I set the “painter’s pallet” looking icon to give the track color, as you allude to - that color does appear to the left, which is your area B. But the area marked C does not change regardless of the Color Strength setting in Preferences. If I set it to MAX, the track does not get the same color as B; in fact, it does not change at all.
A side note…and something well worth reading up on and practicing a little…
Templates are great when you’re in a position to start from scratch; but, what if you have big project already in the works and wish to automate the process of making swaths of changes to the project view like: rearrange, colorize, sort, shrink/expand (folders), hide/show, rename, etc?
Project Logic Editors can be used to ‘batch edit’ tracks/parts/elements based on various characteristics. I.E. Patterns in track names. Track Type, Container Type, Color, Etc…
Hence, it’s possible to reconfigure all sorts of things about your Project View using a sort of booleen logic, including setting colors of various elements of the GUI. I.E. You could have a one key command built that would seek out all grey audio tracks with the pattern “kick” in their name and turn them blue, then find any audio elements/parts in the track with the pattern ‘(A)’ in their names and turn those red. Then launch another logic editor that seeks out patterns ‘(B)’ in the element/part names and turns them yellow. Etc…
This stuff comes in handy for projects of all sizes, and if you do anything with 50 or more tracks, it can be a MAJOR time saver in finding/sorting/tagging stuff so it pops out and is easier to see/find/work-with.
A related thought and #feature-request - the ability to apply a newer version of a template to a project that was based on a previous version of said template. Let me explain: I have a template for new songs that I change/improve about once a week, mostly with minor changes. However, if I start a new song based on that template, I am now stuck with that version of that template for that song, and would love to be able to import the latest changes from my ever-evolving template into that song. At times, when things get too out of sync, I just create a brand new song from a much newer version of that template, and then painstakingly import tracks from an older song into it, just so I can take advantage of the more recent changes of that ever evolving template. Having an automated way for such changes to “ripple through” or “be inherited” by songs that are based on an evolving template would be incredibly useful to me!