We use databaseManager.hasRecordChanges() in a form’s onHide() event to detect if there are changes to the current record. If changes are detected, we query the user to either save or discard the changes.
In 6.1.0, hasRecordChanges() does not recognize that a field has been changed unless the field has lost focus. This is different behavior from 6.0.7.
In 6.0.7, if the user changes only one field and does not tab out of that field, then closes the form, hasRecordChanges() returns ‘true’.
In 6.1.0, if the user changes only one field and does not tab out of that field, then closes the form, hasRecordChanges() returns ‘false’.
hasRecordChanges() should detect field changes regardless of the field focus.
In 6.1.0, if hasRecordChanges() does not detect the field change, then our query to save/discard the changes is bypassed.
In case sample calling setAutoSave(true) saves outstanding changes so this is why no changes are seen afterwards. The behavior is the same in 6.0.7 and 6.1.1 .
In case sample calling setAutoSave(true) saves outstanding changes so this is why no changes are seen afterwards. The behavior is the same in 6.0.7 and 6.1.1 .
So is this actually NOT a bug Laurian? The operation works as it did in 6.0.6 and 7? I ask because we have been waiting for this as a bug fix since it was reported before we upgrade to 6.1.
In case sample calling setAutoSave(true) saves outstanding changes so this is why no changes are seen afterwards. The behavior is the same in 6.0.7 and 6.1.1 .
So is this actually NOT a bug Laurian? The operation works as it did in 6.0.6 and 7? I ask because we have been waiting for this as a bug fix since it was reported before we upgrade to 6.1.