Help with clear screen !!

[vingori]

Hei,
I use the following code within my TACL script for the clear screen
functionality:

======================================================================
== 6530 terminal control.
== Parts of this can be used like this:
== #output [T6530:ClearScreen]
======================================================================
[#def T6530 struct
begin
byte byte0 value 7;
char Bell redefines byte0;
byte byte1 value 27;
char esc redefines byte1;
byte byte2 value 36;
char Dollar redefines byte2;
byte byte3 value 37;
char PerCent redefines byte3;
byte byte4 value 38;
char Ampersand redefines byte4;
byte byte5 value 64;
char CursorPos redefines byte5;
byte bytes6 (0:1) value 27 73; == clear screen
char ClearScreen (0:1) redefines bytes6; == escape sequence
byte bytes7 (0:1) value 27 74; == clear to end of page
char ClearEOP (0:1) redefines bytes7; == escape sequence
byte bytes8 (0:1) value 27 75; == clear to end of line
char ClearEOL (0:1) redefines bytes8; == escape sequence
end;
]

======================================================================

======================================================================
== ClearScreen
== Homes the cursor on a 6530 terminal and clears the screen.
======================================================================
[#def ClearScreen routine |body|
#output [T6530:esc]H[T6530:esc]J
] == ClearScreen

-- This script is borrowed from another reference material.

Now whenever I call the 'ClearScreen' routine...it does clear the
screen, however when the new screen appears I expect the following to
appear:

Text message 1 -> Display only
Text message 2 -> Display only
Text message 3 -> Display only
Text message 4 -> Display only
Text message 5 -> Display only
Choose a option: _? --> expecting the users input

Unfortunately I don't see a consistency in what appears. The patter
that I see after the use of ClearScreen is:

1.
Text message 4 -> Display only
Text message 5 -> Display only
Choose a option: _? --> this is expecting user input

2.
Choose a option: _? --> this is expecting user input

3.
Text message 1 -> Display only
Text message 2 -> Display only
Text message 3 -> Display only
Text message 4 -> Display only
Text message 5 -> Display only
Choose a option: _? --> this is expecting user input

Most of the time I have to scroll up to find my text messages. I
suspect I'm using the wrong co-ordinates within the ClearScreen
routine, but when I refer the manual & some snippets I find similar co-
ordinates elsewhere...Can someone clarify?

rgds,
vin.

[mustlearntandem]

I'm sure there are more purist methods, but I do it the old fashioned
way with #DELTA:

?section cls macro
#FRAME
#PUSH CS CLEAR
[#DEF CS DELTA |BODY| 27I IH$ 27I IJ$]
#SET CLEAR [#DELTA/COMMANDS CS/]
#OUTPUT [CLEAR]
#UNFRAME

[Tom P]

> routine, but when I refer the manual& some snippets I find similar co-

> ordinates elsewhere...Can someone clarify?
>
> rgds,
> vin.

That 6530 Programming Manual is still available..

[Keith Dick]

It really would help if you showed a complete sequence of commands that causes this problem to occur. Your description leaves a lot to our imagination.

When you scroll up to find the text messages, do you find that the first text message appears at the beginning of the terminal memory? That is, if you scroll up until the terminal will not scroll any more, is the first text message always on the first line of the screen? If yes, then I would say that the clear screen sequence probably is working correctly. It looks okay, so I imagine it is right.

One simple explanation I can think of is that the TACL commands that you use to prompt for user input are accidently outputting something that you do not intent which either is causing the screen to roll up a few lines or is displaying around 20 blank lines or a similar number of line feeds or some other unintended output that has the result of making the terminal scroll up a few lines.

If examining your TACL code does not reveal anything like that, please construct a small example, test it to make sure it exhibits the problem you described above, then post the whole small example so we can look at the actual code you are using.

[Bill Honaker]

One other pertinent piece of information could be what is acting as
the '6530' in this case. Is it a real terminal, or an emulator. If
it's an emulator, which program and version is it. This may be an
emulator bug of some sort.

On Thu, 13 Jan 2011 09:01:33 -0800 (PST), vingori <vin...@gmail.com>
wrote:

[MicroTech]

And, pushing the KISS principle a little, here's another #DELTA
implementation:

?SECTION cs MACRO
#frame
#push delta
#set / type delta / delta 27i 73i
#output [ #delta / commands delta / ]
#unframe

Cheers,

Henry Norman
MicroTech Consulting
https://sites.google.com/site/microtechnonstop/

[Chuckles55]

On Jan 13, 12:37 pm, Tom P <werot...@freent.dd> wrote:
> On 01/13/2011 06:01 PM, vingori wrote:
>

<... snipped extra text...>

>
> That 6530 Programming Manual is still available..

Hi,

I did a Google search on "6530 Programming Manual" and got nothing. I
did find references to TN6350 programming codes in "ftp://cs.utk.edu/
pub/shuford/terminal/tandem_terminals_news.txt". Anyone know where I
can get a copy of the manual, its addendum, or (at least) a list of
the escape-codes ?

Chuck

[Joachim Schmitz]

What's wrong with http://www.hp.com/go/nonstop-docs , which sooner or later
should should lead you to
http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c02118581/c02118581.pdf?

Bye, Jojo

[Chuckles55]

Hi Joachim,

Thanks for the link. I did try to use the first link, but a search of
"6350" yielded nothing like the programming manual. Perhaps I didn't
know the correct keywords. I do, very much, appreciate the second link
and have now downloaded the manual.

Thanks again for the assistance,
Chuck

[dimandja]

Thanks Jojo! I don't know why that manual was so elusive before.

[Joachim Schmitz]

Well, not sure what 6350 is supposed to be, but 6530 should have found it
;-)