Rodrigo Vilar
Rodrigo Vilar
> * [ ] Almost all scores take more space for the same measure -> the sheet becomes longer (more height). Would be nice to reduce the space used, or...
> The width calculation should be in `VexFlowMusicSheetCalculator.calculateMeasureXLayout()`. It's possible that some adaptations for vexflow 1 should be changed or new ones for vexflow 4 be made, or that the...
Do you agree that the first measure in note_height_bottomline_test_sample is too long?
> Don't you agree that the `| undefined` here is unnecessary? > > ```ts > let prevMeasure: VexFlowMeasure|undefined; > ``` > > this declaration is undefined by definition, so you...
> @rvilarl Also, by the way, this is just a syntax problem in my eyes. That's what I meant. By declaring without initialization, the type is implicitly `|undefined`. And I...
@sschmidTU it is a matter of not calling applyaccidentals
In the page https://lilypond.org/doc/v2.20/input/regression/musicxml/collated-files#test-cases you find: ### Downloading the test suite _The complete set of MusicXML test files contained in this suite can be downloaded [here](https://lilypond.org/doc/v2.20/input/regression/musicxml/MusicXML-TestSuite-0.1.zip) as a ZIP archive._
According to BB [Behind Bars, ed.], for single notes there are two cases: - stems in same direction => tie curves away from stems - stems in opposite direction =>...
There is a lot of info in the book related to ties (several noteheads...) I recommend you to look into it, before going in the implementation.
When it gets complex, I believe that it makes sense. 