Hello:
I'm using screens (in the screen section) to manage IO, and I have several menus implemented this way. The problem I have is that when switching from one display menu-1 to display menu-2, the old screens are not erased but overwritten. So I get this funky display that shows the new screen on top of the old one, and this is not readable.
Is there an option to clear the screen or tell it not to replace the old one?
Thanks!
Mayer
PS: I'm using gnu cobol version 3.0 running on top of linux
On 30/09/2018 5:12 AM, Mayer Goldberg wrote:
Hello:
I'm using screens (in the screen section) to manage IO, and I have several menus implemented this way. The problem I have is that when switching from one display menu-1 to display menu-2, the old screens are not erased but overwritten. So I get this funky display that shows the new screen on top of the old one, and this is not readable.
Is there an option to clear the screen or tell it not to replace the old one?
--- Synchronet 3.20a-Linux NewsLink 1.114Thanks!
Mayer
PS: I'm using gnu cobol version 3.0 running on top of linux
I don't have Gnu COBOL (but I know it is a very good implementation so
it probably follows the standards...)
You may find the BLANK LINE and BLANK SCREEN clauses useful in this regard...
Pete.
--
I used to write COBOL; now I can do anything...
On Monday, October 1, 2018 at 4:36:49 PM UTC+13, pete dashwood wrote:
On 30/09/2018 5:12 AM, Mayer Goldberg wrote:
Hello:
Is there an option to clear the screen or tell it not to replace the old one?
As Pete says: WITH BLANK SCREEN will do it.
In article <bdbff74e-30c6-4ce6-90d6-237bca4b38ca@googlegroups.com>,
Richard <riplin@azonic.co.nz> wrote:
On Monday, October 1, 2018 at 4:36:49 PM UTC+13, pete dashwood wrote:
On 30/09/2018 5:12 AM, Mayer Goldberg wrote:
Hello:
[snip]
Is there an option to clear the screen or tell it not to replace the old one?
As Pete says: WITH BLANK SCREEN will do it.
It is starting to sound like Mr Goldberg has inherited a system and is beginning to realise the depths of 'sure, I can handle that...'
In article <bdbff74e-30c6-4ce6-90d6-237bca4b38ca@googlegroups.com>,Not at all. Mr Goldberg is learning cobol for fun and interest, not planning on earning a living through cobol, and is managing quite nicely with screen sections. :-) I inherited no system... I wish I had access to a mainframe and could have played with cics too, but screens will have to do for now.
Richard <riplin@azonic.co.nz> wrote:
On Monday, October 1, 2018 at 4:36:49 PM UTC+13, pete dashwood wrote:
On 30/09/2018 5:12 AM, Mayer Goldberg wrote:
Hello:
[snip]
Is there an option to clear the screen or tell it not to replace the old one?
As Pete says: WITH BLANK SCREEN will do it.
It is starting to sound like Mr Goldberg has inherited a system and is beginning to realise the depths of 'sure, I can handle that...'
DD
On 10/01/2018 09:34 AM, docdwarf@panix.com wrote:
In article <bdbff74e-30c6-4ce6-90d6-237bca4b38ca@googlegroups.com>,
Richard <riplin@azonic.co.nz> wrote:
On Monday, October 1, 2018 at 4:36:49 PM UTC+13, pete dashwood wrote:
On 30/09/2018 5:12 AM, Mayer Goldberg wrote:
Hello:
[snip]
Is there an option to clear the screen or tell it not to replace the old one?
As Pete says: WITH BLANK SCREEN will do it.
It is starting to sound like Mr Goldberg has inherited a system and is beginning to realise the depths of 'sure, I can handle that...'
I still blame academia. :-)
bill
On Monday, October 1, 2018 at 4:34:27 PM UTC+3, docd...@panix.com wrote:
In article <bdbff74e-30c6-4ce6-90d6-237bca4b38ca@googlegroups.com>,
Richard <riplin@azonic.co.nz> wrote:
On Monday, October 1, 2018 at 4:36:49 PM UTC+13, pete dashwood wrote:
On 30/09/2018 5:12 AM, Mayer Goldberg wrote:
Hello:
[snip]
Is there an option to clear the screen or tell it not to replace the old one?
As Pete says: WITH BLANK SCREEN will do it.
It is starting to sound like Mr Goldberg has inherited a system and is beginning to realise the depths of 'sure, I can handle that...'
DD
Not at all. Mr Goldberg is learning cobol for fun and interest, not planning on earning a living through cobol, and is managing quite nicely with screen sections. :-) I inherited no system... I wish I had access to a mainframe and could have played with cics too, but screens will have to do for now.
On Monday, October 1, 2018 at 4:42:18 PM UTC+3, Bill Gunshannon wrote:
On 10/01/2018 09:34 AM, docdwarf@panix.com wrote:
In article <bdbff74e-30c6-4ce6-90d6-237bca4b38ca@googlegroups.com>,
Richard <riplin@azonic.co.nz> wrote:
On Monday, October 1, 2018 at 4:36:49 PM UTC+13, pete dashwood wrote: >>>>> On 30/09/2018 5:12 AM, Mayer Goldberg wrote:
Hello:
[snip]
Is there an option to clear the screen or tell it not to replace the old one?
As Pete says: WITH BLANK SCREEN will do it.
It is starting to sound like Mr Goldberg has inherited a system and is
beginning to realise the depths of 'sure, I can handle that...'
I still blame academia. :-)
bill
What for? :-)
On Tuesday, October 2, 2018 at 3:22:56 PM UTC+13, Mayer Goldberg wrote:
On Monday, October 1, 2018 at 4:34:27 PM UTC+3, docd...@panix.com wrote:
In article <bdbff74e-30c6-4ce6-90d6-237bca4b38ca@googlegroups.com>, Richard <riplin@azonic.co.nz> wrote:
On Monday, October 1, 2018 at 4:36:49 PM UTC+13, pete dashwood wrote:
On 30/09/2018 5:12 AM, Mayer Goldberg wrote:
Hello:
[snip]
Is there an option to clear the screen or tell it not to replace the old one?
As Pete says: WITH BLANK SCREEN will do it.
It is starting to sound like Mr Goldberg has inherited a system and is beginning to realise the depths of 'sure, I can handle that...'
DD
Not at all. Mr Goldberg is learning cobol for fun and interest, not planning on earning a living through cobol, and is managing quite nicely with screen sections. :-) I inherited no system... I wish I had access to a mainframe and could have played with cics too, but screens will have to do for now.
I never bothered with SCREEN SECTION, too tedious (and anyway my systems were originally developed in COBOL 74. You can DISPLAY working-storage items UPON CRTRichard,
(or however). I would setup a 2000 character screen image in W-S and then redefine this naming just the input fields. Set the colour to background, display the whole screen, set the colour to foreground and display the input fields then for each input field set the colour to input display and accept the field AT linecol.
I then (this is early 80s) wrote a screen generator that would take a text file of the layout with a list of the input/output fields and generate the W-S and the COBOL code to display the screen and accept the fields.
The 'list of input/output fields' included the field's name, order of entry (zero if it was just a display field), a prompt to be displayed at the foot of the screen, a paragraph name to be used to validate the field, other stuff.
Then I shifted to using Flexus SP2 which is even nicer.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,064 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 148:01:28 |
| Calls: | 13,691 |
| Calls today: | 1 |
| Files: | 186,936 |
| D/L today: |
33 files (6,120K bytes) |
| Messages: | 2,410,931 |