scratching my head.. it's beginning to look like we're walking parallel here, is it possible we're talking about different things?
just let me roll my sleeves and explain the nature of the actual working problem, instead of just talking about keyframes. (and no science!)
taking a step back, which might seem unnecessary, but can't help suspecting there lies the real root of the misunderstanding. you might wanna go get coffee, this'll take a while.
while budding green and oblivious to a:m, i'm an animator and the tools for making motion look a certain way are the first i care about. (materials, lights, focal lengths and their rendering is the scary part.) the channel window is familiar to me, and it's the one i work in. i'm very disappointed in having to change windows for just moving a selection of keys every time, and that will be my next e-mail to the powers that be! the other window is naturally helpful in seeing all the keys, if you need to match placement, but it's like once every twenty times..
so, entering 3D, with this particular script, the first rule and a very personal perspective is to not make it look like 3D animated till almost at the end of the film. the look will be a cut out animation made in studio, with a camera.
an animator builds that visual component with motion. here, in this case, the motion is not allowed to be the fluid CG smoothness.
this is achieved simply by discarding the default operations, and choosing "linear" as interpolation method. number eight.
when i opened the interpolation dialogue, i was alarmed to see no checkmark appear to show my choice.
thinking, "uh-oh... this is not in widespread use.." i expected trouble, and trouble came swiftly.
major problem: when i'm in the zone, i'm just this big flaming passion happening. stopping to do searches for changing default interpolation in project settings feels like killing a live being, killing the flame for good.
so every new keyframe was in bezier equation, and evey ten frames i had to stop to select a bunch of keys and press eight for linear.
when using linear, the other interpolation you often want is hold, number seven. it's a speedy way to animate, and blends right in when in linear environment.
and there's no way to tell which keys are eights and which are sevens.
so when choosing the last ten-ish keys to eight them, i frequently overwrote my sevens. over and over again.
just please don't tell me to remember the numbers of the frames, anyone! or write them down, or something like that. not gonna happen. this is one place i'm expecting a program to adjust to me, not the other way around. i want the keyframe square, default color red, to change its color when i choose another interpolation.
the reason i spoke about the background is, well quite simply, "don't come with a problem come with a solution". i thought about ways to improve this function, and it seemed that if the dark grey background would be white (just like in the other timeline), you'd get two grey shades for use in keyframe colors straight away. right? then add black and you've one color missing. figured a black frame with white in the middle would show, even in that tiny format.
the window size
was a problem, and a big one, i told you in another thread. but that was not the issue here. two monitors sounds like the perfect solution, i'll start choosing lottery numbers...

man that's a lot of text. but that's the whole kaboodle with whiskers and all.
anyone got this far.. i'm curious as to people's workflow - this is a good representation of my MO, how does it work for others?