Robin, I'm very grateful for your careful explanations. I have studied them as others study Revelation, and yea, I begin to affirm that I am enlightened. Or on the track at least. I didn't see that non-command events don't propagate. And in the situation I was describing -- a mouse-click in an STC that's inside (is the child of) a Frame -- it's the native control, the library code for the STC class, that originally gets the click. If so, then I see why, when I try to bind the click in the frame (only), then *nobody* in my code apparently gets the click, because the library code has exhausted it. Is that right?
I notice that I accidentally said, and you incidentally confirmed, that two different classes can bind the same event. (The child STC binds its "own" mouse-click and acts on it; the parent Frame binds its child's mouse-click and acts on it in some other way.) That's interesting, and I don't remember seeing this in the documentation. I suppose there's no possibility of competition -- the event has just one "home", and we're just adding *extra* behaviors in response to it. Hm.
Charles Hartman
Professor of English, Poet in Residence
Connecticut College
http://cherry.conncoll.edu/cohar
http://villex.blogspot.com