Skip to main content

[archive] Escape Key

  • December 1, 2006
  • 7 replies
  • 0 views

[Migrated content. Thread originally posted on 01 December 2006]

We start our first program with an initial screen setting. After that all other screens are opened as floating screens. When we are at our initial screen and we hit the escape key our program closes without performing any other procedures.

I have added several steps in exectption event other an in our event where we stop the thread and when I try and run through debug as soon as escape is pressed the screen closes and no other steps in the program are executed.

Is there a way to prevent this from happening?

7 replies

[Migrated content. Thread originally posted on 01 December 2006]

We start our first program with an initial screen setting. After that all other screens are opened as floating screens. When we are at our initial screen and we hit the escape key our program closes without performing any other procedures.

I have added several steps in exectption event other an in our event where we stop the thread and when I try and run through debug as soon as escape is pressed the screen closes and no other steps in the program are executed.

Is there a way to prevent this from happening?
Are you also looking for exception values (not just events), you should be able to get an exception value of 27 from the escape key.

[Migrated content. Thread originally posted on 01 December 2006]

We start our first program with an initial screen setting. After that all other screens are opened as floating screens. When we are at our initial screen and we hit the escape key our program closes without performing any other procedures.

I have added several steps in exectption event other an in our event where we stop the thread and when I try and run through debug as soon as escape is pressed the screen closes and no other steps in the program are executed.

Is there a way to prevent this from happening?
Yes I am looking for both. When I am in debug after esc is hit I never return to debug. It looks like the escape key is killing the wrun32.exe.

[Migrated content. Thread originally posted on 01 December 2006]

We start our first program with an initial screen setting. After that all other screens are opened as floating screens. When we are at our initial screen and we hit the escape key our program closes without performing any other procedures.

I have added several steps in exectption event other an in our event where we stop the thread and when I try and run through debug as soon as escape is pressed the screen closes and no other steps in the program are executed.

Is there a way to prevent this from happening?
I see what you mean. It is based on the accept method. The tour.cbl when run in debug does not go away with the escape key whereas many of the other sample programs do.

[Migrated content. Thread originally posted on 01 December 2006]

We start our first program with an initial screen setting. After that all other screens are opened as floating screens. When we are at our initial screen and we hit the escape key our program closes without performing any other procedures.

I have added several steps in exectption event other an in our event where we stop the thread and when I try and run through debug as soon as escape is pressed the screen closes and no other steps in the program are executed.

Is there a way to prevent this from happening?
where is the tour.cbl program is it in the sample programs?

[Migrated content. Thread originally posted on 01 December 2006]

We start our first program with an initial screen setting. After that all other screens are opened as floating screens. When we are at our initial screen and we hit the escape key our program closes without performing any other procedures.

I have added several steps in exectption event other an in our event where we stop the thread and when I try and run through debug as soon as escape is pressed the screen closes and no other steps in the program are executed.

Is there a way to prevent this from happening?
Yes, tour is in the samples that Acucorp distributes.

[Migrated content. Thread originally posted on 01 December 2006]

We start our first program with an initial screen setting. After that all other screens are opened as floating screens. When we are at our initial screen and we hit the escape key our program closes without performing any other procedures.

I have added several steps in exectption event other an in our event where we stop the thread and when I try and run through debug as soon as escape is pressed the screen closes and no other steps in the program are executed.

Is there a way to prevent this from happening?
Try adding the line : SET ENVIRONMENT "QUIT_MODE" TO "27".

[Migrated content. Thread originally posted on 01 December 2006]

We start our first program with an initial screen setting. After that all other screens are opened as floating screens. When we are at our initial screen and we hit the escape key our program closes without performing any other procedures.

I have added several steps in exectption event other an in our event where we stop the thread and when I try and run through debug as soon as escape is pressed the screen closes and no other steps in the program are executed.

Is there a way to prevent this from happening?
Went into the initial programs properties and checked the box on the first screen Prompt when program exits.

This is what we needed now the user is asked Quit? before exiting.