Typical VolumePage behavior is to wrap cells down to the next row if the VolumePage is to narrow to fit all cells in 1 row. This usually results from the parent window being shrunk either by scripts or a user manualy dragging the edge of the window.
When the VolumePage wraps cells down to the next row, the parent page doesn't automatically stretch vertically to fit the new row. If they started out the same size, you end up with the now taller VolumePage getting cropped by the parent window.
You could set an OnHoverOut script to force the parent page to match the VolumePage size, but that would only work if they are intended to be the exact same size.
In any case, yes shoving group member pages into a Volume page will almost certainly kill the data. It MIGHT work if you replace the top page with a VolumePage and preserve identicle nesting and object names. I say might because I've tried similar replacements where only the object type was changed and it broke hard-coded text updates.
IMO, the easiest way to auto-size the group window is to create layout buttons that assign OnShow and OnHide scripts for each member page which in turn sets maximumsize and minimumsize. Let the hard-code do its auto-repositioning. Prety much the same method used for most bag mods.
|