Hm,
I think ObservableList can hardly make such guarantees as that would be
implementation dependent, and thus FXCollections can't give such
guarantees either.
I suppose ObservableList could mandate this (just as Collection classes
can mandate a specific equals/hashCode behavior for valid
i
Hi,
ObservableList defines bulk operation methods like 'setAll', 'addAll',
'removeAll' etc. It does not specify that these operations should fire one
change. On the other hand, FXCollections relies, at least on 'setAll', to
have this behavior in the methods 'copy', 'fill', 'reverse', 'rotate' etc.
