Documentation for IDCount functions

[looeee]

There are four IDCount functions:

• THREE.GeometryIdCount()
• THREE.MaterialIdCount()
• THREE.Object3DIdCount()
• THREE.TextureIdCount()

They are part of the API (can be accessed via THREE.GeometryIdCount() etc. ) so they should be documented.

The question is, where? Should they get a separate page, or be included in the Geometry, Material... pages?

[aardgoose]

Note GeometryIdCount is also used by BufferGeometry which may influence your choice, which would tend to indicate a separate page, to avoid duplication. Not sure how useful they are though.

[mrdoob]

These are not supposed to be accessible to the user. Now that we're using modules should be easy to hide them. I'll see if I can work this out.

[mrdoob]

GeometryIdCount is still pending to be removed. Will leave it for the next cycle though.

[looeee]

OK, I'll leave this open for now

[Mugen87]

We can't remove GeometryIdCount() like the other functions because both BufferGeometry and Geometry need to share the same ID generation. Should we agree to keep the function and close the issue?

[looeee]

I'm OK with this, although the functions should be documented if they are exposed

[Mugen87]

Then i would suggest to document GeometryIdCount() for now and note that the function is intended for internal usage only.

[dubejf]

You could use even/odd Ids for BufferGeometry and Geometry and increment by two to get rid GeometryIdCount().

[mrdoob]

You could use even/odd Ids for BufferGeometry and Geometry and increment by two to get rid GeometryIdCount().

Interesting! 😀

[Mugen87]

Indeed! 😊 We should give this a try!

[mrdoob]

Actually, I don't even know why GeometryIdCount() was public...

[mrdoob]

Okay. This can be closed now.
Thanks @dubejf!