Kbase P154600: Procedure Editor compile error dialog does not appear when indirectly called from .NET form
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/11/2009 |
|
Status: Unverified
SYMPTOM(s):
Procedure Editor compile error dialog does not appear when indirectly called from .NET form
Compile error dialog does not appear in front of Procedure Editor when non-compiling code is entered and F2 or Shift-F2 is pressed to check the syntax.
If F2 or Shift-F2 is pressed a second time, the dialog appears, but neither keyboard nor mouse input are recognized.
Dotted line on OK button of error dialog indicates that it is selected, but the button does not respond.
prowin32 process must be killed to escape from the modal dialog.
Clicking outside of the Procedure Editor window or keyboard input such as ALT-TAB pressed before F2 or Shift-F2 makes the compile error dialog appear.
If the compile error dialog is made to appear before a second F2 or Shift-F2 is pressed, a second F2 or Shift-F2 will dismiss the dialog and Procedure Editor may be used normally.
FACT(s) (Environment):
Procedure Editor is invoked programmatically from ABL window which is invoked from .NET form
Windows
OpenEdge 10.2A
CAUSE:
Bug# OE00193204
FIX:
None at this time. The problem can be worked around if the user is aware that the compile error dialog does not fail to execute; it is merely not visible. Any interaction with the desktop outside of the Procedure Editor window will make the dialog appear.