Re: Outline line numbers problem WDSC V7.0.0.8

Hi,

It works fine for me on v7.0.0.8i, and did on all previous versions of WDSCi 7. The only issue I see is that sometimes the line numbers listed in the outline view do not correspond to the *number* of the line that the cursor is positioned to, even though the cursor is positioned to the item I selected. (Something to do with statement and source line numbers, I think.)

These may be simple responses, but they are easily overlooked: Have you refreshed the outline? Are you absolutely certain that the correct files, data structures and copy books that your source uses can be found in the library list of the connection you used to open the source member? The outline uses the library list of the connection to find the definitions of the objects used to build it, and files with extra fields (for example) can cause the kind of problems that you have mentioned.


Cheers,
Paul.


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Sami Gabizon
Sent: 26 May 2009 09:50
To: WDSCI-L@xxxxxxxxxxxx
Subject: [WDSCI-L] Outline line numbers problem WDSC V7.0.0.8

Hi,

I have a problem which prevents me from using V7.

When I generate an outline for an RPGLE source, I get the usual sections
of Files, Data Structures, Fields etc.

When I expand any of the sections and click on a name, let's say a field
name, the cursor position in the source is automatically changed to show
where the field is defined.

Now, when I expand the list of line numbers where the field is used in
the source and click on one of the lines, the source is not positioned
to the line. In fact, it seems that the RSE is not responding. When I
click on the source body and use the down arrow key, I see that the
cursor is positioned one line below the line that I wanted to see.

This behavior was the same in all version of V7.



I have V6 installed and working as expected in the same pc, but since
the outline is not working in V7 I cannot switch to it.



I have uninstalled V7 and installed it again. I tried it on another pc
with a new windows install and the problem remains.



I searched the archives and didn't find any reference to this problem.



Does anybody know how to fix the problem?

Thanks for any reply.



Sami Gabizon