[bonninr]

The generated panel draws each divisional piston in its own division's column. The generals stay in Pistons.

Fixes #489.

Changes

• The GrandOrgue import writes the manual's division on each of its divisionals (DivisionID on the Combination row).
• The definition loader reads it into Combination::divisionId.
• panelSections() puts a combination that has a division in that division's section; one without stays in Pistons.

Test

functional.ui.panel-divisionals: two manuals, each with divisionals named "1" and "2" (the Walcker Wildervank naming), and one general. Each manual's divisionals land in its own column; the general stays in Pistons. Full functional pass on Windows: 301 run, 0 failed.

Checked in the program

The GrandOrgue demo with two divisionals named "1" and "2" drawn on each of its three divisions, a generated panel, Fit on, graphics only, Windows:

build	where the divisionals are
main	all six in Pistons, three "1"/"2" pairs between the generals
this branch	"1" and "2" at the foot of Pedal, First Manual and Second Manual; Pistons holds the generals only