Whenever a user makes changes to a data-aware control, the corresponding dataset will fire the OnDataChange event when the user leaves the control (eg, by pressing an OK button, or going to the next data-aware control).
That's OK for most data-aware controls, but not for a spin edit control. Because the up and down arrows are pictured as actual buttons, the user will expect an immediate data change and not a delayed one.
As an example: I have a form, that contains a button, that will only be enabled if all controls on the form are properly filled. The last control on the form, happens to be a TsDBDecimalSpinEdit control. So the user has filled in all controls correctly, including the spin edit, but at that moment the button does not become enabled. The user has to leave the spin edit control for the button to become enabled.
So, DeveloperExpress solved this by adding the Boolean property ImmediatePost to their SpinEdit control. This throws a DataChange event as soon as the spin edit changes value. A very nice feature.
Is quite usable in AC too.