In my application I have an entity that has a transient field which is calculated from other fields. That entity is bound to a form using a binder and that computed field is also displayed (although as read-only-field only, i.e. the binder’s setter for this field is null).
Now I added a safety-dialog to the form that asks the user - when leaving the form - whether he/she doesn’t want to save the data.
The condition for bringing up that dialog is based on the binder.hasChanges() method. But for some reason, even if I changed absolutely nothing, the binder seems to “believe” that there were changes and my suspicion is, that it is this calculated field that it considers (for whatever reason) a having changed because that’s the only one that I set “manually”, i.e. that is not being set by the binder itself but by application code.
Can I somehow flag this field as not to be considered for the hasChanges()-method?