Inconsistent face ordering between hex and boundBox

From code inspection the face definitions in boundBox appear to be wrong - different face order than the hex cellModel, inverted face normals.

For code-style: the treeBoundBox enum for FRONT/BACK, TOP/BOTTOM could be misleading since TOP in this case designates +y and not +z as may be expected.

Will send additional notes per email.

The face numbering (but not face normals) in treeBoundBox follows from the coordinate ordering and does not relate to the hex cell shape.

Reassigned to @mark

Faces and implicit normals in boundBox are wrong. Fortunately not used anywhere at the moment.

Will add some further cleanup for boundBox at the same time.

mentioned in commit 15cd5e9f

Status changed to closed

mentioned in commit 4acf33ef57a84f4c8b8dfa962b040871901c0d41

mentioned in commit 4db667e2ea352787cd52d02eec2db603e861a425

mentioned in commit 59f9914eee1e7324efd6e67a4480f694da3bf5f0

Mentioned in commit 15cd5e9f

Mentioned in commit f1a58247e9f564bade4285472b40192e8f9ea1d0

Mentioned in commit 26c420262795dbaeb5fc8aa8470d0dba7c8e85de

mentioned in commit 13612811

mentioned in commit c20bb920