Kbase P121859: 4GL/ABL: Debugalert stack trace dialog appears when user chooses F1 as the default RUN key.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
30/09/2008 |
|
Status: Unverified
SYMPTOM(s):
4GL/ABL: Debugalert stack trace dialog appears when user chooses F1 as the default RUN key.
Debugalert stack trace dialog appears when user chooses the F1 function key to run an application in a session where the F1 function key is defined to be the default RUN key.
If the session is started with a customized .ini file that defines the F1 function key as the default RUN key, then choosing the F1 key opens the stack trace dialog.
The stack trace dialog box should appear only on the CHOOSE of the HELP button by the user.
The session startup command line is:
prowin32 -debugalert -basekey ini -ininame Custom.ini
Where Custom.ini is a customized .ini file with a line in its [Proedit] section defining the F1 function key as the default RUN key. For example:
[Proedit]
RUN=F1
FACT(s) (Environment):
Windows
OpenEdge 10.1x
CAUSE:
Bug# OE00136242
CAUSE:
This is a product limitation on Windows operating systems only.
FIX:
Use one of the following workarounds:
1. Do not define the F1 function key as the default RUN key in either a customized .ini file or the Windows registry.
2. Use the Windows default F2 function key as the default RUN key.
3. Define a function key other the F1 function key as the default RUN key if the F2 function is not available.