Vincent Goudard

I am struggling to synchronize the output of jit.gl/phys.picker with my patch.

Namely, jit.gl.picker does not support @automatic 0 mode, and as jit.phys.picker is concerned, I am not aware of any possibility to access jit.phys.* internal clock (is there ?)

Here is a concrete and simple scenario where this gets me stuck:

When the user click (or touch) the screen:

- if an object was clicked, send the output data to the object

- if no object was clicked, do something else

How would you implement the following scenario without using an arbitrary delay.

Without any notification and/or external scheduling info/command, I didn't find a better workaround than waiting an arbitrary delay before deciding if something was picked or not.... But I'm hoping for a better phys world.

Not to mention the fact that this solution will quickly get messed up if several touch are triggered at time interval below the delay...

Here is a concrete and simple scenario where this gets me stuck:
When the user click (or touch) the screen:
- if an object was clicked, send the output data to the object
- if no object was clicked, do something else

Without any notification and/or external scheduling info/command, I didn't find a better workaround than waiting an arbitrary delay before deciding if something was picked or not.... But I'm hoping for a better phys world.
Not to mention the fact that this solution will quickly get  messed up if several touch are triggered at time interval below the delay...

jit-phys-picker-and-jit-gl-picker-synchronisation-clock

Sorry, I posted the wrong patch. Here it is.

This patcher aims at being able to have the 3 following picking situation handled :

1 - I did pick an object, and want to control it with native jit.phys.picker interaction (body1)

2 - I did pick an object, and want to control it with my own custom interaction (body2)

3 - I did not pick an object, and to do something with it (the blue/pink dot)

So far, it does the job with an ugly delay, and it mainly shows how unconvenient it is.

Now consider how cool it would be when jit.gl/phys.picker also report something on its outlet when nothing is picked.

Now more ugly delay, no more messy patch (or say, significantly less messy patch).

This patcher aims at being able to have the 3 following picking situation handled :
1 - I did pick an object, and want to control it with native jit.phys.picker interaction (body1)
2 - I did pick an object, and want to control it with my own custom interaction (body2)
3 - I did not pick an object, and to do something with it (the blue/pink dot)

So far, it does the job with an ugly delay, and it mainly shows how unconvenient it is.
Now consider how cool it would be when jit.gl/phys.picker also report something on its outlet when nothing is picked.
Now more ugly delay, no more messy patch (or say, significantly less messy patch).

jit.phys.picker and jit.gl.picker synchronisation clock