Re: [open-cobol-list] Improvement to screen handling.

[Michael Anderson]

@Dave :-)
the good'ol days when terminal I/O was simple and very fast.

On Linux my back-tab works!
Gnome-Terminal would always hijack my F1 key, xterm eliminated that!

On windows you may want to try Xterm.
Using Xterm I had some Fkey problems, and fixed as follows.

xterm  -title "OpenCOBOL" -sb -sl 1200 -geo ${COLS}x36 -fg ${FG} -bg ${BG} \
        -cr red -fn ${FONT} -fb ${BFONT} -xrm \
        'XTerm*VT100.translations:     #override \n\
        <Key>F1:                string(0x1b) string("OP") \n\
        <Key>F2:                string(0x1b) string("OQ") \n\
        <Key>F3:                string(0x1b) string("OR") \n\
        <Key>F4:                string(0x1b) string("OS") \n\
        <Key>F11:               string(0x1b) string("[23~") \n\
        <Key>F12:               string(0x1b) string("[24~") \n\
        Button1<Btn2Up>:        ignore()' \ &



On 01/26/2014 05:49 PM, David Black wrote:
> Some thoughts on how we solved the back-tab problem in the past.
> Years ago when there were no terminal standards we wrote our screen
> drivers that we used in all of our software products in Assembler use
> Curses. We had one driver for each brand of terminal and came up with an
> 18 character address scheme that contain X,Y,Color,Data Size,Data Type,
> etc.  The driver had a push/pop stack of 900 bytes (50 addresses) in it
> to hold (Push) each "accept" command as it occurred. If a "Forward Tab"
> was issued it was treated as an (Push) "accept" for stack purposes. (The
> screen was defined as a table of 18 bytes addresses) The table would
> take you to the next address in the table when you entered the return
> command. If you entered a "Forward Tab" it would go to the normal next
> address and store the address as it would do with a normal "accept". If
> a person then entered "Back Tab" the program would (Pop) the address and
> go to that location.
>
> If the screen was erased the push/pop stack was erased and the cursor
> was placed at the location of the first "accept"
>
> Worked for years without any problem. If I had it to do over I would
> have more than 18 bytes for an address to solve font, height, and color
> addressing. Times have changed since and more features have been added
> to terminals.
>
> A number of years ago the drivers were re-written in COBOL to eliminate
> the Curses problem. We did not uses any special compiler libraries to
> keep portability between  different COBOL compiler.
>
> Just some thoughts,
>
> David Black
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> open-cobol-list mailing list
> address@hidden
> https://lists.sourceforge.net/lists/listinfo/open-cobol-list