Laurent Pugin

Results 399 comments of Laurent Pugin

> Neon interface: the 'insert' panel contains the examples of the two-tails up/down liquescent (I am not sure how these were implemented) Yes, Neon uses a fork. We are working...

I am working on it. I've done some more significant refactoring than planned, but it will be ready before MedRen.

@martha-thomae please review the [PR](https://github.com/rism-digital/verovio/pull/3718)

@bigorenski your log does not have a call to `RedoLayout`, does it?

I am closing the issue since there is not enough information to do anything about it. Please re-open with more details if needed.

These are the images of the visual test failing ![chord-layout-dots-2-1](https://github.com/musescore/MuseScore/assets/689412/b800f146-476e-44b2-bade-eb67bef5df83) ![chord-layout-dots-2-1 ref](https://github.com/musescore/MuseScore/assets/689412/c9c072d9-a203-4d67-886c-efad7b2920f2) I am not sure what the difference is?

To give a little more background to the PR. When deleting rests when there is more than one voice, a `location` gap is added in the MuseScore file. A gap...

> But what about those failing unit tests? Sorry, I missed these. I'll have a look.

It solves problems (such as in the MEI exporter) where the gap is filled with a rest that is actually not representing the duration of the gap. This seems like...

(PS as it stands, MuseScore inserts a dotted half note rest for the `9/16` gap, which is one 16th note too long)