Nested beam crash on sequence with Stem Direction change

[arshiacont]

The following crashes:

{[ \staff<1> 
   \clef<"f4"> \meter<"2/4"> \stemsUp \beamBegin:1 \beamBegin:2 d-1/16
 \stemsDown d1/16 \stemsDown g/16 \stemsDown d/16 \beamEnd:2 \beamEnd:1 \stemsDown \beamBegin:1 \beamBegin:2 b&0/16
 \stemsDown b&/16 \stemsDown d1/16 \stemsDown b&0/16 \beamEnd:2 \beamEnd:1 ]
  }

while this one doesn't:

{[ \staff<1> 
   \clef<"f4"> \meter<"2/4"> \stemsUp \beamBegin:1  d-1/16
 \stemsDown d1/16 \stemsDown g/16 \stemsDown d/16 \beamEnd:1 \stemsDown \beamBegin:1 \beamBegin:2 b&0/16
 \stemsDown b&/16 \stemsDown d1/16 \stemsDown b&0/16 \beamEnd:2 \beamEnd:1 ]
  }

Note that we restored the use of nested beams as of issue #58

In the debugger, I can see a call to SimpleBeamList::GetHeadPosition() on GRBeam::checkEndStemsReverse where the beam is Null.

[dfober]

fixed

[arshiacont]

Thanks @dfober . You might have forgotten to Push ? :)

[dfober]

right :-) that's done ! Le lun. 19 août 2019 à 10:09, Arshia Cont <notifications@github.com> a écrit :

…

Thanks @dfober <https://github.com/dfober> . You might have forgotten to *Push* ? :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#86?email_source=notifications&email_token=AADJHQZBQ6WLNHG3S6S6VD3QFJIKDA5CNFSM4IMKVZFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4SB4OY#issuecomment-522460731>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADJHQ4A2AFULXPAYAMCTJDQFJIKDANCNFSM4IMKVZFA> .