[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

987.0. "LIST Func. with Duplicate Lines?" by THAV07::MANAKA (Information at your fingertips) Mon Jul 06 1992 04:50

I have a extremely detail-specific customer, and I need help from someone who
knows LIST function.  When you try to list a file with LIST function, or when
you read mails and documents, ALL-IN-1 displays the last line of the previous
page at the top of the next page.  How could I tell ALL-IN-1 not to display
the overlapping line?  Is there any magic words that I shoud say before
reading or calling LIST function?

Let me explain in more detail...  When I read a document or a mail, the 1st
page looks like this:

------------------------------------- TOP --------------------------------------
Line 1
Line 2
    :
Line 19
Line 20
Hit Return to continue {CR}
Line 20
Line 21
    :

I'm not sure exactly the last line # of a displayed page,  but what my
customer doesn't want is that the Line 20 in above example displayed twice.
Please help me...

Thanx in advance,
Clyde.
T.RTitleUserPersonal
Name
DateLines
987.1Customize OA$LISTIOSG::BUTTONMon Jul 06 1992 11:5013
    
    Clyde,
    
    The displaying of the last line of the previous page at the top of the
    next page is how LIST is intended to work.  This is done within the
    Bliss code, so cannot be changed by the customer.
    
    However, the customer could customise the OA$LIST form, to change the
    named data for the NEXT SCREEN and CR options, so it calls
    OA$LIST_FWD_LINE after OA$LIST_FWD_SCREEN.  This will give the customer
    the desired effect.
    
    Jon
987.2Of course, the customer is "always" right . . .IOSG::SHOVEDave Shove -- REO-D/3CFri Jul 10 1992 16:5812
    It's meant to work like that - user input suggests that it's better to
    have one "overlap line" when moving from screenful to screenful. It
    helps the reader maintain context.
    
    Both NOTES and VMS $TYPE/PAGE do the same thing.
    
    As .1 says, you could customise it if your customer _really_ wants to
    (but I bet his/her/its users will ask for it to be uncustomised pretty
    quickly!)
    
    Dave.