Hi, Bryan.
BS>  JM> I originally did this, but the problem (and point of the thread)
BS>  JM> is that it doesn't explicitly show the call to my subroutine in
BS>  JM> the source.
BS> That, to my mind, is a major problem with Delphi (and maybe other 
Visual"
BS> languages). When you have a copy of the source code in your hand, you 
still
BS> don't know everything about the program.
I don't think it's the "visual" situation - after all, you can view the
.DFM in ascii too, if you want documentation of the visual aspects, what
properties are set, etc.
I think the problem (if it is) that you guys are discussing comes from
inheriting behaviour from a parent object, one for which you don't
necessarily have the source. And that can happen with any OO language.
Personally I don't find it it to be a problem, although I'm very glad
I've got the VCL source for when I want to modify some behaviour of the
provided components. Like, say, a TDBNavigator with the buttons
*vertical*. :-)
And mostly you don't even have to do that, the components they give you
seem to have been very well thought out. The other day I wanted a
TStringGrid to have some columns right-justified - just a few lines of
code in an OnDrawCell event.
Regards, fIM.
---
 þ * þ Aids is a behaviorally acquired and preventable disease.
---
---------------