picked event is delayed by almost 300ms which causes wrong entity picks

[blickfeld7]

compared to the old mouseclicked event on viewer.scene.input the new "picked" event of the viewer.cameraControl is delayed and can therefore cause weird behaviour on picking the entity.

A click and mouse move within the delay will not pick the desired 3d entity in the viewer, but the currently hovered entity at the time of the event firing.

[Amoki]

This probably comes from the DoubleClick. The code has to wait to see if there is a second click or not.
If you don't use any DoubleClick feature, you can disable it with

cameraControl.doublePickFlyTo = false;
cameraControl.panRightClick = false;

[blickfeld7]

1. The code for "picked" should not wait for a double click. If someone wants to implement single click and double click "picked" events at the same time, he needs to take care of the timing, handling ect. by himself.

2. If however you want to stick to the idea of having the single click "picked" event to wait for the double click "picked" event the passed entity in the event args should still be the entity you clicked. As mentioned above: currently the provided entity is the one hovered at the time the event is triggered (300ms after actual click).

So either way: right now the event is pretty useless and a bug in my opinion. I'd prefer the 1st solution however.
BTW: we're also using the doublePickFlyTo at the same time with the old "mouseClicked" event and it works perfectly. If it wouldn't I'd rather turn off doublePickFlyTo before having 300ms delayed "picked" events.

[devjta]

Well, the viewer.scene.input.on and mousedown and dblclick are working like your first idea, which I dont like at all..

It would be better to give an attribute/property to the method, if we want this behavior or not. I dont mind waiting 300ms, before firing the mousdown event.

[blickfeld7]

I'm currently using viewer.scene.input.on, but as i understood they're going to be private and we should use the events implemented on the viewer's CameraControl object.
As of 1.3.42 the event is still fired with delay, but the hit entity is the one at click time, not the one which you're hovering at the time of event firing.

So to me this issue is solved. The delay is not nice for the user experience, but i can live with it.

[devjta]

Oh, you are right it also works with "picked" at cameraControl.. I find it kinda strange that there is no warning.. Also the examples are also still using the scene.input.

At least the new listener has no double-click/tap issue anymore! So thanks for your answer :)

[devjta]

Great.. with the newest verison this hoovering error is fixed, but for whatever reasons at a PixelC tablet the "picked" get triggered TWICE.
Same codebasis at the desktop (also Chrome) works without any problem -> 1 click = 1 picked event...

[blickfeld7]

as of 1.4.1 this got worse. Now the delay is also applied with cameraControl.doublePickFlyTo = false; might pick the wrong element stated in my last comment now #333 (comment)

[Amoki]

May it be the ray cast that takes ~300ms on a slow computer so the "picked" event is emitted later than expected?