[archive] "Wait Processing" message | Rocket Forum

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

Page 1 / 1

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

I'm struggling with the same problem.
Just wanted this thread to be read again to get some help.

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

In the installation folder of ACUCOBOL-GT, there you will find subfolder acucblxxx\\AcuGT\\sample\\samplprj\\source.

Where xxx is your version number, for instance 700.

Among the samples here, there are three files:

custrpt.cbl
bldcust.cbl
cancel.cbl

which illustrates a technique of building a data file while displaying a cancel dialog.

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

In the installation folder of ACUCOBOL-GT, there you will find subfolder acucblxxx\\AcuGT\\sample\\samplprj\\source.

Where xxx is your version number, for instance 700.

Among the samples here, there are three files:

custrpt.cbl
bldcust.cbl
cancel.cbl

which illustrates a technique of building a data file while displaying a cancel dialog.

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

In the installation folder of ACUCOBOL-GT, there you will find subfolder acucblxxx\\AcuGT\\sample\\samplprj\\source.

Where xxx is your version number, for instance 700.

Among the samples here, there are three files:

custrpt.cbl
bldcust.cbl
cancel.cbl

which illustrates a technique of building a data file while displaying a cancel dialog.

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

Ghisle,

Included a very small project concerning a paged grid without threads.

If the grid is changed in ACTION = ACTION-PAGED-FIRST, then a small wait-window is displayed while filling the grid, and destroyed if the grid is filled.

If one generates the ACTION-PAGED-NEXT, the grid automaticly fills in the rows as much as needed. In this procedure, also the ACTION-PAGED-PREVIOUS, we would like to see the same wait-window displayed and destroyed when the procedure ends.

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

I am sorry Hans, I have no time to look at this, you will have to take it with Tech support.

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

No problem.
I'll post Piet Henskens' ideas...

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

No problem.
I'll post Piet Henskens' ideas...

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

No problem.
I'll post Piet Henskens' ideas...

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

Ghisle,

Piet Henskens says the issue is not a technical problem.

My following question then :

If you change a grid in Modify Grid1, Action = Action-Paged-Next, the runtime automaticly knows how much records need to be read in order to fill the grid.

Is there an internal variable that we can use where the number of records-needed is hold like event-data-2 ?

This way I could manage the problem myself.
Txs

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

According to documentation, the action Action-Paged-Next generates an event MSG-PAGED-NEXT. When MSG-PAGED-NEXT triggers, EVENT-DATA-2 contains the number of READ NEXT you have to do to fill the page. Is this what you are looking for?

This event occurs for grids with the PAGED style. It indicates that the user has clicked on the "Next Record" button. The expected response from the runtime is to supply the next record after the end of the grid's current data. To do this, add a new record at the end of the grid (using RECORD-TO-ADD). If the data is from an indexed file, the value of EVENT-DATA-2 is the number of READ NEXTs you need to perform to get to the appropriate record. This value is controlled by the property FILE-POS. See the discussion on the FILE-POS property under the grid control for details on how this works. If you cannot supply the next record (because you have reached the end of the file), respond by setting EVENT-ACTION to EVENT-ACTION-FAIL. When you do this, you receive no more MSG-PAGED-NEXT events.

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

Ok Ghisle,

I reprogrammed the grid routines using File-pos, not using the automatic handling of grid by the runtime.

Now I can use a 'Wait message' any way I want.

One last question though.
When the grid is filled, the runtime has to do a huge task of processing, meanwhile the wait message is displayed.

If a user keeps the page-down or page-up keys down, I want the grid filled once instead of continuous generating a Msg-Paged-NextPage / PrevPage. The same behaviour has to occur when they click the grid's symbol for next page / previous page.

So the user has to wait while the grid is filled in order to click or push a button to get the next page.

Any suggestions here ?

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

Ok Ghisle,

I reprogrammed the grid routines using File-pos, not using the automatic handling of grid by the runtime.

Now I can use a 'Wait message' any way I want.

One last question though.
When the grid is filled, the runtime has to do a huge task of processing, meanwhile the wait message is displayed.

If a user keeps the page-down or page-up keys down, I want the grid filled once instead of continuous generating a Msg-Paged-NextPage / PrevPage. The same behaviour has to occur when they click the grid's symbol for next page / previous page.

So the user has to wait while the grid is filled in order to click or push a button to get the next page.

Any suggestions here ?

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

Ok Ghisle,

I reprogrammed the grid routines using File-pos, not using the automatic handling of grid by the runtime.

Now I can use a 'Wait message' any way I want.

One last question though.
When the grid is filled, the runtime has to do a huge task of processing, meanwhile the wait message is displayed.

If a user keeps the page-down or page-up keys down, I want the grid filled once instead of continuous generating a Msg-Paged-NextPage / PrevPage. The same behaviour has to occur when they click the grid's symbol for next page / previous page.

So the user has to wait while the grid is filled in order to click or push a button to get the next page.

Any suggestions here ?

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

When I work on controls and don't want user interaction, I use to disable the controls.

Have not tried this on the grid though, may be that is an alternative?

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

I tried this but when I set the GRID to DISABLED when the user pressed the symbol to get the next page, the symbol stays down so it keeps on generating Paged-NextPage and the runtime crashes.

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

Well, whatever it does, it should certainly not crash. I suggest you report it to Tech Support.

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

Well, whatever it does, it should certainly not crash. I suggest you report it to Tech Support.

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

Well, whatever it does, it should certainly not crash. I suggest you report it to Tech Support.

[Migrated content. Thread originally posted on 23 February 2006]

I need a technique to display a "wait" message while loading a grid. I've tried a modal independant window displaying the window and wait screen (read only entry field with a message) at the start of the "first page message event" and destroying the screen after the load. This works fine for the first go. But subsequent displays on page down, page up etc do not show the screen only the blank window.

Vins Nash

Hans,

I received your question but wood like to receive either the program you used that caused the problem so I can adapt it to use i.e. the data from the list.dat file created by the demo program pagebox.cbl or a working demo as I need your exact code to reproduce the problem.

Best regards,

Piet
Techsupport Benelux