scene.onPointerUp firing twice.

[Pryme8]

http://www.babylonjs-playground.com/#36TFT6#5

Just like the title says, I am getting double fires on the pointer up response.

[pichou]

Yes, I noticed the same thing. 

Had to use a test to ignore the second trigger.

[Pryme8]

so like:
var ignoreFlag = 0;
...onPointerUp... {
         if(ignoreFlag){return;}
         ignoreFlag = ignoreFlag?1:0;
}

or something like that?

[RaananW]

https://github.com/BabylonJS/Babylon.js/issues/3908

[RaananW]

sorry, bug closed

This is by design. the onpointerup is fired twoce - once for the TAP event and once for POINTERUP. you can check for type in your callback and react to only one of them.

[Pryme8]

Ah gotcha!  Thank you sir.  That clears things up.
Shouldnt the types of the responses be pointerup and touch?

@RaananW
Both of the events I see are registering as pointerType:"mouse"
http://www.babylonjs-playground.com/#36TFT6#12

[RaananW]

The right way to go would be this - http://www.babylonjs-playground.com/#36TFT6#14

onPointerUp is amazingly useful, but technically deprecated. The type is not broadcasted there (thou I see no reason not to do it, honestly. I will add type later as a 3rd variable for people still using this function)

[Pryme8]

well damn...

I need to go over these observables.

http://www.babylonjs-playground.com/#36TFT6#15
Now I have all the pointer events under that one observable. cool, thanks!

[pichou]

Thanks @RaananW! 

Works perfectly with observables. So does it mean that we have to always use obvervables instead of onPointerUp/Down because they will not be maintained anymore?

[Pryme8]

They keep everything reverse compatible for the most part, so I assume the old methods will be left alone but in documents and tutorial the newer ones will be showcased.

[RaananW]

It is  always recommended to use observers, but we will keep things backwards compatible, so those onPointerUp callbacks will stay there.

I actually added the "type" as a 3rd parameter to the onPointerUp callback  in a recent pull request, so you can continue using the single callback. but again, observers are the future!