Alberto wrote:
I think that having both of the above constraints (ie. "regardless of
the telnet client and terminal emulation") will end up leaving you in
the dark without a solution.

for reasons too numerous to expound on, if you can soften either of
these, you may stand a chance.

you imply that you are locked into your current "client emulator" due
to some of the features; however, my advice would be to re-examine the
features your current emulator and see if there isn't indeed a solution
there (towards opening another window/context/dialog-box..) and if not
to seriously consider alternatives. there are numerous options
available to you by going the latter route from shareware emulators
supporting multiple sessions... to emulators with features enhanced for
communicating with a pick server.

(as a less ideal approach, if you can lock into a certain "emulation",
you may be able to locate the equivalent of an I/O bridge server that
can sit between your telnet terminal emulators and the pick server and
be intelligent enough to switch session contexts, repainting the screen
when necessary. such screen solutions existed for unix boxes, ap/pro,
and i'm certain if you dig a little that you could locate one for NT.
again, this assumes you are able to relax the criteria for being
completely emulation-independent.)

Point taken. But I think if someone where to start with the SUI
routines they could get the idea of how to handle various terminal
definitions and be able to use the idea of keeping a memory stack and
repainting the screen in order to accomplish the task Alberto asked
about. Refresh my memory please, are the SUI routines freely available
or only to those who own AccuTerm?

BTW, I love AccuTerm, the SUI library and the GUI library. They are
easy to use and I have found AccuTerm to have the best emulations
around. I have tried many others and always seem to find pieces missing
in them, AccuTerm has everything I need in one tidy little package.

Marshall

Peter Schellenbach wrote:

Alberto -

As I mentioned in a previous post, the SUI routines that come with
AccuTerm will do "windowing" with a real Wyse 60 or VT420 terminal,
using page memory and the block copy function. If your telnet client
emulates Wyse 60 or VT420, and includes the block copy function and
page memory, you can use the same technique. When you open a window,
copy the current screen to a different page using the block copy
function. Clear the rectangle that defines your "window" and let your
program update any characters within that window. When you want to
close the window, use the block copy function to copy the saved screen
back to the live screen. Window nesting depth will be limited by the
number of pages your terminal or emulator supports. I think real Wyse
60 and VT420 terminals come with 2 pages, which is a bit limiting.
AccuTerm lets you define up to 25 pages.

Marshall -

The SUI copyright notice says anyone can use the library, but you
cannot distribute it without permission. It comes free with AccuTerm.

Thanks,

Peter

"Albe" <coralbe_nospam (AT) email (DOT) it> wrote:

Maybe the real question here is exactly which telnet client are you
using? Via Duct? Winnix? Anzio? Procomm? ...

As Dave said, if you have strict requirements that your options are
more limited. I think the only solution you have at the moment is to
custom-code your use of the screen using a mapped array (dimensioned
or dynamic, doesn't matter), and rather than using PRINT/CRT or INPUT
statements your're going to need to modify your array then repaint
your entire screen (or a section of it if your code is more
sophisticated).

In other words you will need to do this on your own because you are
not using tools already have this feature.

Buona fortuna e ciao al'Italia.
Tony