Re: Block printing lines in LPEX - Last Change Date included

On 4/12/2016 10:51 AM, John Yeung wrote:

On Tue, Apr 12, 2016 at 10:06 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

I did a bit of poking, and found that this command will print the date
and sequence number but not the graphical lines created by Ctrl-Shift-O.

Interesting.

I don't know what "graphical lines" are. Are these horizontal rules
(like the old HTML <hr> tag)? Do they persist after you close out of
RDi? If so, is there any artifact stored in the source member on the
i?

I'm sure there's an official name, but I don't know what it is. If you
used RDi, you could press Ctrl-Shift-O and see them for yourself :-)
They are vertical lines and horizontal arrows which connect the tops and
bottoms of control blocks, for example IF and ENDIF. If there's
nesting, there is one line for each control block. Makes it easier to
follow logic in code where a control block is a hundred lines long and
nested 12 deep :-/

They are created on the fly, and as far as I can tell, not stored with
the source member in the cache. They are not persistent; RDi won't show
them tomorrow. I didn't try to look through all of the workspace to see
if there are other places this might be squirreled away.

Then the whole idea of line dates... I understand how SEU handles
them, but how does LPEX? Does it keep track of changes to individual
lines itself? That is, does it try to replicate what SEU does? (I can
see how this might be accomplished, with the subtle difference that
RDi is not 5250, and thus changes would register immediately.)

Yes, in general RDi attempts to emulate SEU in this respect.