Kbase P110830: With keep_old_field_api set to YES comboValueChanged fires when a record is added.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/15/2005 |
|
Status: Unverified
FACT(s) (Environment):
Dynamics
SYMPTOM(s):
With keep_old_field_api set to YES comboValueChanged fires when a record is added.
With keep_old_field_api set to NO comboValueChanged is not fired when a record is added.
With the old smartDataField API's comboValueChanged fires when a record is added.
With the new smartDataField API's comboValueChanged does not fire when a record is added.
CAUSE:
The new API behavior is correct. Standard static Value-Changed triggers also DO NOT fire when a record is added.
FIX:
To implement the new behavior with the old API's (keep_old_field _api set to YES), modify viewer.p addRecord and comment out the loop where valueChanged is run for each combo. i.e.:
/* For dynamic combos who are a parent to another dynamic combo we need to force a valueChange to ensure that the child combos are refreshed */
/* IF glUseNewApi = FALSE THEN */
/* FOR EACH ttDCombo */
/* WHERE ttDCombo.hViewer = TARGET-PROCEDURE */
/* NO-LOCK: */
/* RUN valueChanged IN ttDCombo.hWidget. */
/* END. */