Kbase P180805: 4GL/ABL: The ENTER key does not work in EDITOR widgets if an ABL window is called from a .Net form (
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/20/2011 |
|
Status: Unverified
SYMPTOM(s):
4GL/ABL: The ENTER key does not work in EDITOR widgets if an ABL window is called from a .Net form (.Net UI WAIT-FOR).
The RETURN key does not go into the EDITOR widgets if the application uses the GUI for .NET style WAIT-FOR statement.
The ENTER key does not work in the EDITOR widget if an ABL window is called from a .NET form (.Net UI WAIT-FOR)
The ENTER key fails in GUI EDITOR when the GUI window has been started from a .NET form
FACT(s) (Environment):
Windows
The CTRL-ENTER causes the works at all times in the in EDITOR widgets whether GUI for .NET style WAIT-FOR statements are used or not.
OpenEdge 10.2x
CAUSE:
Bug# OE00200780
CAUSE:
This is not a bug. This is expected behavior because the Windows Operating System will decide on its own whether the ENTER key goes to the EDITOR or not unless the EDITOR widget RETURN-INSERTED attribute is explicitly set to TRUE.
FIX:
Explicitly set the EDITOR widget RETURN-INSERTED attribute to TRUE either programmatically before the widget is displayed using code similar to:
ASSIGN
EditorWidgetName:RETURN-INSERTED IN FRAME FrameName = TRUE.
Alternatively, check the RETURN-INSERTED attribute in the property sheet of the EDITOR widget at design time in the AppBuilder.
If you are working in an AppBuilder generated Window, insert the following line of code before the DISPLAY statement in the enable_UI procedure.
EditorWidgetName:RETURN-INSERTED IN FRAME DEFAULT-FRAME = TRUE.