The text in the description is a bit amateurish:
Return the body's moment of inertia. This is usually automatically computed from the mass and the shapes. Note that this doesn't seem to work in a
_readyfunction: it apparently has not been auto-computed yet.
The words "seem" and "apparently" give an impression that the it's not known for sure. Since this is the official documentation, it should be stated what it is (or isn't), not that it "seems" to be.
(Sorry if this sounds harsh. It is certainly better than no documentation, but I think it can be improved and I don't quite have the time to check right now).
Maybe it just needs to be revised to explicitly state it requires at least one physics frame to process before it will provide a valid value.
Returns the body's moment of inertia. Automatically computes inertia from associated
[class CollisionShape]s' mass during physics frames, after the [code]_ready[/code] function has
triggered.
...or something?
This whole doc is in need of a rewrite. The doc sprints have been focused on filling in undocumented classes, but this one could use some love as well.
Might be worth grepping the docs for uses of words like "seem", "apparently", "probably", "maybe" to find potential candidates for "unprofessional"/"I wasn't sure about it" docs.
Most helpful comment
Might be worth grepping the docs for uses of words like "seem", "apparently", "probably", "maybe" to find potential candidates for "unprofessional"/"I wasn't sure about it" docs.