Recommendations for beams

[rpatters1]

I would like to see some "should" recommendations added to the events placed into beam instances. These would be to achieve maximum portability.

Events in beams

• Should all come from the same sequence in each measure that the beam has events. That is, events should not come from two different sequences within the same measure.
• Should all come from sequences on the same part staff in beams that cross barlines.
• Should specify event.staff values to cross staves, rather than selecting events from separate sequences on two different part staves.
• Should all come from sequences with the same part voice when a part staff has multiple voices.

If the committee feels that any of these should be "must" instead of "should", I would consider refactoring beams to enforce the "must" conditions, if possible.

[rpatters1]

I saw the notes from today's meeting. I am wondering if we should consider moving the beams array into sequence. Obviously, there would be no way to enforce the rule just because it was moved there. But it would show intent.