After sound-on-sound midi recording, plays back right but displays "wrong"

Hi, 
 
Here's a link to a screengrab which helps explain the problem.
 
http://i1159.photobucket.com/albums/p637/ling_yai/Sonar%20screengrab_PRV%20and%20Clip%20midi%20view%20mismatch_zpsnalekvt8.jpg
 
I had an existing midi clip of some block chords.  The original note data consisted of everything in the bottom half of the screengrab, i.e. in the PRV, *except* the two notes I've circled in red.
 
I wanted to record key switch data for use with the Kontakt library which the midi is playing through. The keyswitch is C2 (which triggers a strumming pattern.) 
 
So I went to Preferences and set recording to sound on sound, and specified to store takes (I only did one take anyway) in a single track,  armed for recording, pressed play, and played the two sustained C2 notes you see in the red circles.
 
It recorded and plays back fine -- sound on sound recording worked -- the original notes are there, and so is the added keyswitch performance. 
 
But as the screengrab shows, the clip in the Tracks view, between measures 11 an 27, looks as though I used overwrite as the recording mode, i.e. it looks like there are now only the two C2 notes, but no longer any chords.
 
I was expecting the clip to show all of the same midi note data seen in the PRV. It's supposed to, isn't it?
 
Anyone seen this? Any advice?
 
I hope I can fix or understand this, it seems really quirky and counterintuitive.  Even though it plays back ok, I'm not ready to say, all's well that ends well, and just make a new note for my growing collection of "Sonar quirks" post-it notes i.e. "Just remember in the future that sometimes, the view of midi in the clips pane should be completely ignored because it's only partially true." I don't want to have to inspect the PRV for each midi part to find out what's really going on.
 
I'd be grateful for any help.
 
 

Read the manual chapter on Take Lanes, maybe you'll find that things are more logical than it seems, even if they don't work as initially one would expect.

Having said that, I also would like to have the option of not creating a new clip for each take.

I had studied about take lanes earlier, but only for audio. I assumed midi would work the same. Oh well, live and learn. Thanks for the posts.

It's not that these shortcomings are crippling. For example, just now I followed the kind advice here and boom, ok, now I've bounced the clip, everything is ok.
 
They're just so .... very contrary to what I'd expect, after 18 years of DAW use. There are a lot of counterintuitive quirks to learn, a process which still takes up a lot of my time and tends to douse inspiration. (That's one reason I'm still perching at Hopkinton, so I can at least deal with a static corpus of quirks, rather than having to start the process anew each month) (Ok, to each his own, I don't want to start a pillow fight on that here). I do seem to spend an unusual amount of time puzzling over unexpected Sonar behavior, whether they are bugs or "ununsual features," for someone a few months now into the learning curve.  
 
I'm still cautiously open to the idea of investing further study and making Sonar my home DAW (unless I hit some unremediable show-stopper, which I hope never happens). But I would never recommend it to a DAW newbie, it could well put them off of a potentially great hobby. Just too many WTF moments. I'd send 'em to Studio One, MULab, Mixcraft or even N-Track. Not as fully featured as Sonar, but you sure can dive in and just use them.