If the current/selected record index of a form foundset is for example 7, and Servoy automatically unloads the form, when the form is restored/reloaded in its onLoad callback the form foundset state is restored and its current/selected record index is still 7, however Servoy fires the onRecordSelection anyway - even though the record selection did not change.
Is this a bug or intended behavior? Why onRecordSelection is fired in this case - the selection did not really change?
If you try something like this: foundset.setSelectedIndex(foundset.getSelectedIndex()) - basically setting the selected index to the same value, the onRecordSelection callback is not fired (which is to be expected). We are having problems with this erroneous onRecordSelection callback during form automatic re-load because we need certain code to be executed only once when the selection is changed and there is no way to distinguish if the onRecordSelection was fired due to a "genuine" selection change or because of that form re-load.
Any information on this will be appreciated.