Feedback
Did this article resolve your question/issue?

   

Article

PDSOE: List of widgets in Add Trigger is incomplete

Information

 
TitlePDSOE: List of widgets in Add Trigger is incomplete
URL Name000057413
Article Number000173186
EnvironmentProduct: OpenEdge
Version: 11.x
OS: Windows
Other: Progress Developer Studio for OpenEdge, PDSOE, AppBuilder perspective
Question/Problem Description
PDSOE: List of widgets in Add Trigger is incomplete.

In Developer Studio OpenEdge editor, the list of fields to generate trigger events is not complete.

ABL window contains many widgets.

Only a subset of the available widgets are available displayed for selection in the Widget drop-down of the Add Trigger dialog.

The following comment is found in the code when viewing the source code of the ABL window in the OpenEdge ABL Editor:
/* DEFINE FRAME statement is approaching 4K Bytes. Breaking it up */ 

Problem does not occur in the standalone Appbuilder.

For example, adding a trigger in the AppBuilder results in the following:

User-added image

All fields are available in the standalone AppBuilder's Section Editor.  

In PDSOE, the Add Trigger dialog only presents a subset of the available fields:

User-added image

Even if a scroll bar is present on the drop-down, the list of widgets is incomplete.
 
Steps to Reproduce
Clarifying Information
Trying to add triggers to widgets using the AppBuilder perspective of Developer Studio.

Problem occurs regardless of where the Add Trigger dialog was opened, e.g. from the ABL UI Designer or the OpenEdge ABL Editor.

 
Error Message
Defect/Enhancement NumberDefect PSC00326255 / ADAS-3071
Cause
The exact cause is not known at this time.
Resolution
Until the fix is available, use the workaround below.
Workaround
Option #1
In Developer Studio add the trigger for another field and then manually edit the field name reference in the Editor.  If necessary toggle off:
Window-Preferences->Progress OpenEdge->AppBuilder->Editor->Make AppBuilder generated code read-only
This will allow all sections to be modified.

Option #2
Create a new dummy window, use the wizard to generate the required code and copy that to the failing window, including the preprocessor directives (&...).

Option #3
Use the classic Appbuilder to create the trigger and re-open the file in the PDSOE.
Notes
Last Modified Date3/8/2019 3:05 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.