Kbase P147713: Changes to ABL Inherited Form properties are used incorrectly when a form instantiating the control
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/14/2009 |
|
Status: Unverified
SYMPTOM(s):
Changes to ABL Inherited Form properties are used incorrectly when a form instantiating the control is open
Instances of the control that were dropped onto the form before the control was changed show their previous properties in Visual Designer
Instances of the control that were dropped onto the form after the control was changed show their new properties in Visual Designer
Code overriding control properties with the new values can be seen in the InitializeComponent method from code view.
If the control is changed again while the instantiating form is closed, and the instantiating form is reopened, the earlier changes that were added to the InitializeComponent method of the form will override the new changes in the control itself.
FACT(s) (Environment):
Windows
OpenEdge 10.2A
CAUSE:
Bug# OE00184276
CAUSE:
An instance of the control that was added to the form before the control was changed still exists in memory when the form has not been closed. References to that instance are still valid, so Visual Designer uses that instance rather than re-instantiating the control. It sees the differences in the second (post-change) instance of the control on the form as overridden properties, and adds them to the form code as property overrides.
FIX:
To work around this problem, close any instantiating forms before making changes to control properties.