When an AttachFilter is executed, CollectionChangeEvent will not fire for elements that already exist.
(WhenTrue/WhenFalse will fire)
If you are performing some destructive operation on a View (GameObject, etc.) with a CollectionChangeEvent, it may be bad if you cannot apply the same process to an already existing element.
When an AttachFilter is executed, CollectionChangeEvent will not fire for elements that already exist. (WhenTrue/WhenFalse will fire)
If you are performing some destructive operation on a View (GameObject, etc.) with a CollectionChangeEvent, it may be bad if you cannot apply the same process to an already existing element.
So I added the following overload:
AttachFilter<>(filter, bool invokeAddEventForInitialElements = false)( It may not be a very pretty solution..)