[log in to unmask] disposes:

> <[log in to unmask]> proposes:
>
>  > Cntl+F (find).

>
>  Well, to be sure, that will work.  It's only that when I am in a few
hundred
>  line procedure and I have to "page-up" forty times to find the procedure
>  name and by then I've forgotten what I was looking for anyway....

I must be dense. We don't have that problem at all with Cntl+F finds. Your
original question was "how can I quickly find every routine that calls a
particular function?" To get that answer almost instantly, type Cntl+F
"function name" and press the "Find Next" key at least once to set in the
search value. After that, you can press the F3 key to perform the find next
function, looking at the top of the coding screen to get the name of the
routine in which the call occurs. Doing this performs the equivalent process
of that Alfredo suggested, but it is very, very quick. I find the editor in
Visual Basic to be as good and as powerful an editor as I've ever used.

QCTerm is a VB program and it's quite large, approx. 150 objects and 300
functions. It now requires 600 pages to print it all out, using a 9pt font,
which is as small as I care to read. What we do (and have always done) for
all of our routines is create a header for each routine that explains what it
is, what it does, and who calls it. If you maintain the header as you go
along, it doesn't add much overhead at all, but it does make complex code
much easier to read months or years later. Here's just a random example:

Private Sub ChangeFontSize_Click()
Rem ************************************************************************
Rem ************************************************************************
Rem
Rem     A ROUTINE TO GO TO THE NEXT AVAILABLE FONT SIZE
Rem
Rem     (Called by ScreenSizeButton_MouseUp and event generated by MENU.)
Rem
Rem     ENTRY:  Assumes the current font is valid for the current
Rem             screen resolution.
Rem
Rem     EXIT: Modifies FontIndex
Rem
Rem ************************************************************************
Rem ************************************************************************
Dim CurFontIndex As Long
Dim dl As Long
Dim NewLeft As Long
     .
     .
     .

Of course, I never really completely trust our own documentation and always
use the Cntl+F method to check to see if the header information is correct
before I do anything drastic.

Wirt Atmar

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *