CODEWITHSUNDEEP
openedgeprogress-4gl
Agnaldo Macedo
Agnaldo Macedo

Reputation: 3

run in on statement trigger

Progress 9, Windows.

Two Button Screen.
B1 e B2.
Both give RUN in another program that is on disk.

B1                                   B2
--                                   --
RUN p1.w.                            RUN p2.w.
MESSAGE "Back from p1".              MESSAGE "Back from p2".

Correct execution

Click on B1. Open p1 program.
Click on B2. Open p2 program.
Close p2. Show "Back from p2".
Close p1. Show "Back from p1".

Execution seems wrong

Click on B1. Open p1 program.
Click on B2. Open p2 program.
Close p1. Do not show "Back from p1". B1 button freezes, no action.
Close p2. Show "Bcak from p2". Button keeps running.

It gives the impression that it places the calls in a "stack" and the last one that enters has to be the first one that comes out. Any way around this?

Upvotes: 0

Views: 175

Answers (1)

Mike Fechner
Mike Fechner

Reputation: 7192

You should run those .w's with the PERSISTENT keyword and avoid executing any WAIT-FOR statement in the main block.

Upvotes: 1

Related Questions