Improve docs of addChild() and setParent() #16073
Conversation
|
Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s). |
|
Sorry @bjsplat, I think I don't have a permission to assign labels. |
|
Snapshot stored with reference name: Test environment: To test a playground add it to the URL, for example: https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/16073/merge/index.html#WGZLGJ#4600 Links to test babylon tools with this snapshot: https://playground.babylonjs.com/?snapshot=refs/pull/16073/merge To test the snapshot in the playground with a playground ID add it after the snapshot query string: https://playground.babylonjs.com/?snapshot=refs/pull/16073/merge#BCU1XR#0 |
|
WebGL2 visualization test reporter: |
|
Visualization tests for WebGPU (Experimental) |
I struggled a lot with using
addChild(). It seemed to mess up the position of the child mesh. I had no idea why, because the documentation only said:It also wasn't clear to me what's the relationship between just assigning to
.parentor callingsetParent().After struggling with these problems for many weeks, I finally read the source and figured out that
addChild()simply callssetParent(), the documentation of which does say what it does with child coordinates.I'd hope this little improvement to the docs will help others to better understand the relationship between these three ways of setting the parent.