ObservableListContentProvider removes elements from a viewer one by one even in case when all these elements was removed from a model at one stroke.
This logic is implemented at ObservableListContentProvider.java:124
As result
1) it is not so fast in case with big number of elements
2) I listen selection of the viewer, and I see several intermediate notifications.

Write your own ContentProvider (Copying the code from the old one) but
in reality the would be nice if one could configure the behaviour so
that e.g. the ListDiff holds a certain amount of data simply a refresh
is done instead of remove.

Tom

Am 10.09.10 13:27, schrieb Yury Chernikov:
> Hi,
>
> ObservableListContentProvider removes elements from a viewer one by one
> even in case when all these elements was removed from a model at one
> stroke.
> This logic is implemented at ObservableListContentProvider.java:124
> As result
> 1) it is not so fast in case with big number of elements
> 2) I listen selection of the viewer, and I see several intermediate
> notifications.
>
> Could you recommend me a way how I can override this behavior?
>
> Yury.