@svanya said:

Subpatches CAN have creation arguments and it is the same one as its parent

I think this is wrong: writing $1 in any subpatch simple take the $1 from the main patch where your subpatch is located. Try to replace $1 with $2 in your main abstraction and see, you don"t get "e" when asking for $1 but still "3".

For the other points I agree, I also discovered them by practising.

@svanya said:

I've been programming pd for over five years and never knew this was possible.
Mark it up as "There is always something new to learn".

That's a positive point of view. I would say that, after 5 years, if you still discover things it might also means that pd has still some work to do on the documentation

Cheers

I agree that pd could have basic abstractions in order to make it more easy like random list etc...

The CEAMMC lib is certainly one of the best exemple of what a good standard lib could be (many basic object with good naming convention etc). But the functions are growing a bit too much and the complexity added by the extending pd with new data types are maybe the limit of such project.

@whale-av
I am finally back on it and made it work finding the clothest X center position of the head and a reset after the last skeleton exit... I don't now how it behaves with many people yet...

@ricky
As far as I can tell, we still need a terrifying windows system in order to get skeleton tracking with Kinect v2.

@whale-av
Actually I think that a user is still detected even if some part (like the head) leave the file of view... so relying on it being "untracked" means there will still be a working ID in the field of view for other parts of the body.

Unfortunately With KinectOSC, there is no global message regarding the tracking of a user, that's why I used the delay between information before for my test.

@whale-av said:

Inferred and tracked

it give information about a specific part of the body so the program can make that part disappear in order to keep a less jittery body on screen I guess (that's the way I will do next).

Using reset will (very) temporarily introduce errors too.....

Yes, I think also that it might be problematic.

I am thinking..... when a head is in the red area it is deleted from the store.......

Yes, that way looks even more suitable!

Wow thanks @whale-av, that looks like a clever way to do!

But If the user who have the lower head leave the field, the remaining user who have the lowest are not present since I reset all (or clear "smallest" text define) isn't it?
The kinectv2 could see up to 6 user, so if many people are in traked in the room how to do?

@jameslo the ID's are generated randomly each time a new user come in the field of view. The second example is just a quick hack to make something "quickly work" but the real attempt is in the patch from the zip file (with a simple Kinect user data simulator)

@ingox the thing is I don't need to find the lowest ID, but to route the list of the ID which contain the smallest Z head position in the list. For example if I have 2 ID incoming:

print: /bodies/000000001/joints/Head 0.321555 -0.0569061 0.2 Inferred
print: /bodies/000000002/joints/Head 0.321555 -0.0569061 0.1 Inferred

then, I need to route only the list which have the smallest head z position:

print: /bodies/000000002/joints/Head 0.321555 -0.0569061 0.1 Inferred

@whale-av I guess you talk about occlusion here, the last list element is trackingState (Tracked, NotTracked or Inferred), I guess I need to think about it also but it's another step ahead.

Anybody on this?

Right now I made a simple rule to route the current ID as long as the body is present.. but It's just a simple patch that I need to improve.

I still need to parse a list regarding the z position of the head...

@seb-harmonik-ar great!
My theme is ready, less confusion between objects and messages boxes for students, and everything is readable

Here is the plugin : colors-plugin.tcl

@seb-harmonik-ar
Thats working perfectly in color-plugin.tcl! Thanks.

Another question regarding inlet/outlet: now the msg_cord color is corelated to iolet outline color.
In order to make even better themes do you think that it would be possible to have a separated outlet outline color? or be able to have no outline in iolet?