[To recap, high level request is:
"Be able to select a data element name in the source and have a function to "find in outline"

So, from a quick experiment, it highlights the lines that contain the text with a outlined yellow arrow in the left margin. (WDSC7.0 is what I have.)

This is definitely new to me.

I do see a couple of drawbacks:

1) I work mostly with the current pane full size. When I do Search->Text->File it goes back to a window, because it brings up the Search Pane.

Of course, from the Search Pane you can use the Up and Down yellow outlines arrows go the previous or next match. And I suppose I could make the search pane a floating view and keep the editing window maximized.

2) The outline view does show where a field is defined. If it originated in a file, outline tells me that immediately. This doesn't

Me, I'd like to see you continue to investigate new outline functionality.

What do others think?


On 1/11/2011 5:27 PM, Edmund Reinhardt wrote:

Sam, Kurt et. al.

Here is a handy tip that will get you want you want, until we can implement
this feature.

Select your variable in the editor, go to the menu Search->Text->File
and then in the Search results view, you will see all occurences of that
string in the file.

See the attached bitmap (I know you won't see it on the wdsc-l)

Is this enough to meet your requirement, or do we need to continue to
investigate this functionality.

Hope this helps,

(See attached file: FindInOutline.jpg)

From: "Lennon_s_j@xxxxxxxxxxx"<lennon_s_j@xxxxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx
Date: 13/11/2010 12:56 PM
Subject: Re: [WDSCI-L] Find in Outline (was Re: Compiling rpg source)
Sent by: wdsci-l-bounces@xxxxxxxxxxxx


Appreciate your participation in the list.

Here's where I'm coming from. Note that I'm current on WDSc 7 (hoping
to upgrade next budget year.)

I'm maintaining/researching a lot of code that I didn't write. It's all
RPG IV, but much of it came from a RPG 3 basis and virtually all
variable names and field names are 6 chars max. I'm not familiar with
all the many files, so when I'm looking at code and want to find the
usage of a variable, I expand the Field section of the outline
and start typing the variable name. Often the variable is found.
However, if this happens to be a field in a file, then I have to expand
the Files section, and then guess which file to expand and try typing
again. Maybe I picked the right file, but often I don't.

There may be better ways to speed up this process, but, it seems to me
that what would be of great value the ability to right click on a
variable name and then choose "Locate in Outline."

I'm not sure hovering (fly-over) could accomplish this.

And, while I'm in at it...

When expanded, many of my outlines get exceeding long. I would be nice
to be able to have a quick way in the outline to collapse all sections.

Thanks for listening,


I would make use of this. We have a lot of variables that start with
"w_" so positioning doesn't work in this case. And when there's a copybook
bringing in 100's of w_ fields, it's a pain to sift through (b/c I'm pretty
sure they are presented in order of appearance in the copybook - vs.
alphabetical). Also - if I'm looking for a DS subfield, and there are 20
DS's, this would make it easier to locate to find the definition.

However, if content-assist could be all that every suggested it could be
in a previous thread, I would rarely go to Outline for field definitions
(for me it's more of a navigational tool).


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of lennon_s_j@xxxxxxxxxxx
Sent: Friday, November 12, 2010 4:41 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] Find in Outline (was Re: Compiling rpg source)

Might be cool to be able to select a data element name in the source and
have a function to "find in outline".

I heartily agree! Anyone else?


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.