Changes for `_processPointerUp ` in alpha 4

Questions
1

Hi,
after update to 4 alpha version saw some differences using simulatePointerUp.
this.scene.simulatePointerUp(...).

Previously onPointerObservable it was triggering just once but now each simulate triggers 2x, once with PointerEventTypes.POINTERTAP and once with PointerEventTypes.POINTERUP.

This comes from _processPointerUp

if (this.onPointerObservable.hasObservers()) {
            if (!clickInfo.ignore && !clickInfo.hasSwiped) {
                if (clickInfo.singleClick && this.onPointerObservable.hasSpecificMask(PointerEventTypes.POINTERTAP)) {
                    type = PointerEventTypes.POINTERTAP;
                }
                else if (clickInfo.doubleClick && this.onPointerObservable.hasSpecificMask(PointerEventTypes.POINTERDOUBLETAP)) {
                    type = PointerEventTypes.POINTERDOUBLETAP;
                }
                if (type) {
                    let pi = new PointerInfo(type, evt, pickResult);
                    this._setRayOnPointerInfo(pi);
                    this.onPointerObservable.notifyObservers(pi, type);
                }
            }

            if (!clickInfo.ignore) {
                type = PointerEventTypes.POINTERUP;

                let pi = new PointerInfo(type, evt, pickResult);
                this._setRayOnPointerInfo(pi);
                this.onPointerObservable.notifyObservers(pi, type);
            }
        }

was it a fix for some issue ? or some feature change ?
is it possible to remove mask for onPointerObservable to just use PonterUp/Down/Move ?

Thank you

2

Well this is the expected behavior as you may want to apply filters based on different scenario.

As the input mechanism starts to because complex, I wrote this test to ensure that there was no regression:
https://www.babylonjs-playground.com/#1GLEJK#5

Here is an example with a filter applied to an observable:
https://www.babylonjs-playground.com/#1GLEJK#7