Nils G. Svedmyr
17-Mar-2014, 01:40 PM
The comboform class still has the same old bug it (always?) have had.
Consider the following simple example:
Object oComboForm1 is a ComboForm
Set Size to 13 100
Set Location to 166 174
Set Entry_State to False
Procedure Combo_Fill_List
Send Combo_Add_Item "{Value 1}"
Send Combo_Add_Item "{Value 2}"
Send Combo_Add_Item "{Value 3}"
Send Combo_Add_Item "{Value 4}"
End_Procedure
Procedure OnChange
String sValue
Get Value to sValue
End_Procedure
Procedure OnCloseUp
String sValue
Get Value to sValue
End_Procedure
End_Object
Drop on a sample view, set break-points on the two "Get Value to sValue" lines; one in OnChange and the other in OnCloseUp
The value will be correct for OnChange but is "out of sync" for the OnCloseUp message, i.e. it trails behind showing the previous value, instead of the newly selected one. Sometimes the OnChange is not suitable to be used and the OnCloseUp event is needed.
Any change of this being fixed?
TIA!
Consider the following simple example:
Object oComboForm1 is a ComboForm
Set Size to 13 100
Set Location to 166 174
Set Entry_State to False
Procedure Combo_Fill_List
Send Combo_Add_Item "{Value 1}"
Send Combo_Add_Item "{Value 2}"
Send Combo_Add_Item "{Value 3}"
Send Combo_Add_Item "{Value 4}"
End_Procedure
Procedure OnChange
String sValue
Get Value to sValue
End_Procedure
Procedure OnCloseUp
String sValue
Get Value to sValue
End_Procedure
End_Object
Drop on a sample view, set break-points on the two "Get Value to sValue" lines; one in OnChange and the other in OnCloseUp
The value will be correct for OnChange but is "out of sync" for the OnCloseUp message, i.e. it trails behind showing the previous value, instead of the newly selected one. Sometimes the OnChange is not suitable to be used and the OnCloseUp event is needed.
Any change of this being fixed?
TIA!