developer_analysis 1.1: one Attribute tab per analysed attribute

Analysis 1.0 took a single attribute while Attribute Initialize creates
any number, so a scene with several developer attributes needed one
Analysis node each. 1.1 mirrors Initialize's interface: a multiswitcher
of Attribute tabs, labelled by the attribute name, each with its own
Enable, Global (min, max, sum, average, ratio, spread) and Element
(change, previous value) toggles, all handled in one pass of the two
wrangles. The edge statistics keep their own toggles in an Edges folder
shown for Class Edge. The unread Type menu is gone: the wrangles skip
vector, string and array attributes by inspecting the attribute, and
integer attributes are analysed as floats like before.

1.0 stays on disk for the hips that use it. Verified headlessly that
1.1 cooks the same dictionaries and element attributes as 1.0 on one
attribute and on edges, and analyses a float and an integer attribute
side by side.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

 otls/sop_lsgalante.developer_analysis.1.1.hdalc | Bin 0 -> 13300 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)

diff --git a/otls/sop_lsgalante.developer_analysis.1.1.hdalc b/otls/sop_lsgalante.developer_analysis.1.1.hdalc
new file mode 100644
index 0000000..3da7b70
Binary files /dev/null and b/otls/sop_lsgalante.developer_analysis.1.1.hdalc differ