Very clear and illustrative explanation, thanks.
In my case I don't use block input, and I don't need stdin input either because I use the pipe mechanism.
How can I get the compiler to only call cob_field_accept ?, without using cob_screen_accept and cob_accept.
I think I could ensure that MF always calls curses when you do a DISPLAY or ACCEPT.
Regards
Perhaps because it is legacy code and the screen section was added later, accepts and displays are made for fields from both the SCREEN and the Working.
Is this what causes the compiler to call different functions?
In the application, DISPLAY AT is used interchangeably for fields from the Working and SCREEN SECTION displays.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For Eugenio
I'll give you an example screen
They are apparently simple, however they have dozens of fields related between tables.
An awk device allows full text searches to be performed with a combination of a dd_ pipe output and a C program that reads the CISAM files.
I can move through the fields with CURSOR-UP and CURSOR-DOWN and the program handles it.
They are all generated by an awk script that takes a base or body that we call with the extension _PA.
It is done field by field, never in blocks.
I never got an email specifying the day chosen.
From: "Juan Carlos Escartí" juanc@users.sourceforge.net
To: "gnucobol" help@discussion.gnucobol.p.re.sourceforge.net
Sent: Thursday, September 5, 2024 12:51:24 PM
Subject: [gnucobol:discussion] SCREEN SECTION
Very clear and illustrative explanation, thanks.
In my case I don't use block input, and I don't need stdin input either because I use the pipe mechanism.
How can I get the compiler to only call cob_field_accept ?, without using cob_screen_accept and cob_accept.
I think I could ensure that MF always calls curses when you do a DISPLAY or ACCEPT.
Regards
[ https://sourceforge.net/p/gnucobol/discussion/help/thread/b95ccc3bd8/?limit=25&page=1#1dc0 | SCREEN SECTION ]
Sent from sourceforge.net because you indicated interest in [ https://sourceforge.net/p/gnucobol/discussion/help/ | https://sourceforge.net/p/gnucobol/discussion/help/ ]
To unsubscribe from further messages, please visit [ https://sourceforge.net/auth/subscriptions/ | https://sourceforge.net/auth/subscriptions/ ]
Perhaps because it is legacy code and the screen section was added later, accepts and displays are made for fields from both the SCREEN and the Working.
Is this what causes the compiler to call different functions?
In the application, DISPLAY AT is used interchangeably for fields from the Working and SCREEN SECTION displays.
For Eugenio
I'll give you an example screen
They are apparently simple, however they have dozens of fields related between tables.
An awk device allows full text searches to be performed with a combination of a dd_ pipe output and a C program that reads the CISAM files.
I can move through the fields with CURSOR-UP and CURSOR-DOWN and the program handles it.
They are all generated by an awk script that takes a base or body that we call with the extension _PA.
It is done field by field, never in blocks.
I'm confused - can you please post a generated (?) COBOL program that does this (or is the title and data "dynamic" from CISAM)?