LODShape observations

I noticed that LODShape behaves differently when placed in its own TransformGroup inside a bigger TransformGroup versus when placed directly in the outer TransformGroup adjecent to many LODShapes.

When placed in the TG->TG (many)->LOD structure, onLODChanged fires as soon as the object is displayed. This is great because it means that I can create the object without any geometry, etc. and set the appropriate one based on the distance to the View.

When placed in the TG->LOD (many) structure, onLODChanged does not fire as soon as the object is displayed. Instead, it only fires the first time an LOD boundary is crossed. If I needed to use this structure (luckily, I don't), it would mean that I would have to calculate the initial distance to the view and pass it into the constructor so the constructor could choose the appropriate LOD to display. This doesn't seem like the intended functionality although the exact timings of onLODChanged are slightly vague.