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

Conference share::zap

Title:Zap Technical Conference
Notice:ZAP Version 5.3 is available. See note 1.1
Moderator:ZAPDEV::MACONI
Created:Mon Feb 24 1986
Last Modified:Mon May 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:170
Total number of notes:492

13.0. "Minor addition to ZAP.MSG, Please?" by GIGI::GREENE (Michael Greene) Thu Mar 20 1986 10:22

    Thanks very much for the tailorable message in V3.4. Thanks also for
    retaining the ability to put the various parameters in the message.
     
    One minor request: Would you please make the escape sequence,
    which positions the message at the home position, part of the message.
    I would like to be able to put the message out following the last
    item on the screen. For example, I'm tailoring the message to just
    be a couple of lines, and I want to "scroll" it on the screen, not
    do direct cursor addressing.
    
    Thanks..
    
    PS The new image exit handler sounds really nice.
    
    Michael
T.RTitleUserPersonal
Name		DateLines
13.1I'll second the motionPICA::HIDERPaul HiderTue Jun 03 1986 01:1633
 
   Zap looks as though it has destinct possibilities..

   I would like to start using Zap on our systems, however, I would like
   to disable the positioning of Zaps messages at the top of the screen.

   The applications we run typically fall in to one of 2 classes
   dumb terminal and scope terminal.

   The scope terminal applications generally trap broadcast messages
   and display them in a 1 line message buffer.  Zap's attempts to output
   at the top of the screen are therefore ignored.
   I plan to use a 1 line message since scope applications are reluctant
   to display more than the first line of broadcast messages.

   The dumb terminal applications treat the terminal as one long stream
   and the cursor is generally on the bottom line of the screen.

   In this case Zap outputs at the top of the screen when one would normally
   expect to see output at the bottom.  Should a regular broadcast message
   come along, Zap's message will be scrolled off the top of the screen,
   undesirable.

   When Zap's final message comes along, it is written to the top of the
   screen, the cursor is then returned to the bottom of the screen and
   the process killed.  The DECserver then regains contol and puts up
   the "Local>" prompt, scrolling Zap's messages off the top of the screen.
   The user is thus left with no indication of the error of his ways..

   Thanks in advance,
			..Paul

   P.S.  are you running the latest notes server? my unseen count won't clear.
13.2Another vote.TWEED::MCDONALDFri Jun 06 1986 12:045
    
    	I would like the messages scrolled also.  Message tends to get lost
    	in the information that is already up there. 
    
    Guy.
13.3Minor 3.4 revisionMRMFG3::K_MACONIThe DoctorMon Jun 09 1986 13:384
    The current version of Zap, Version 3.4, contains the %l qualifier
    in the ZAP.MSG file which disabled screen mode cursor positioning.
    
    This qualifier may be placed anywhere within the text of the message.
13.4help!PICA::HIDERPaul HiderWed Jun 11 1986 01:0930
  
  I copied the latest version of ZAP from MRMFG1 this evening and tried
  the %l quailifier and was unable to get it to work.  The messages are
  still being put at the top of the screen.

  here is my ZAP.MSG file:

!
! Formatting characters available:
!
!	Symbol	Meaning			Display format
!
!	  %a	Accumulated idle time	ZZZ9
!	  %b	Bell			None
!	  %d	Device name		XXXXXXX
!	  %l	Line mode		None
!	  %r	Remaining idle time	ZZZ9
!	  %t	Time of day		DD-MMM-YYYY HH:MM:SS.CC
!	  %u	Username		XXXXXXXXXXXX
!
! Message must be continuous, without comments
!
%l%b%b[ZAP to%u  - You have been idle%a  minutes,%r  until termination.]]

  The message generated is:

[ZAP to HIDER        - You have been idle    1 minutes,   10 until termination.]

  Thanks in advance..
                    ..Paul
13.5Will testMRMFG3::K_MACONIThe DoctorThu Jun 12 1986 09:424
    I will retest that version (3.4-3) and see what happens with your
    command procedure.
    
    		Thanks for the information
13.6still no %lEN::HIDERPaul HiderTue Oct 07 1986 11:016
  
  I am still having the problem with the %l option with Zap V3.5
  that I reported in note 13.4.

    ..Paul
13.7Problem correctedMRMFG1::K_MACONIThe DoctorTue Oct 07 1986 17:538
    
    I thought that this problem was already solved as the testing that
    was performed on Zap showed that the %l option was functioning
    correctly on the system.  However, it turns out that the function
    failed to perform once the message length exceeded 40 characters.
    
    This problem has been corrected in version 3.5-1.  To obtain a
    copy of this version, see note 1.1