Comment Marker Deletion Robustness

[hendursaga]

On the project page, it notes:

Warning: If you manually delete a comment marker in the score and then activate the stale comment, MuseScore will crash trying to select a no longer existing Staff Text. Always use the Delete button from the plugin itself!

Has this been fixed? Is this a limitation of MuseScore? Or could you add checks so that it wouldn't crash, or something?

[jeetee]

I'd consider it a bug in the plugin interface of MuseScore that attempting to select non-existing elements crashes it rather than skipping that element in the selection code.

The cause is that the element pointer the plugin has became a dangling raw pointer to a no longer existing score element.

[hendursaga]

I'd consider it a bug in the plugin interface of MuseScore

I suppose so, too.

Is there a bug filed on this already, for MuseScore?

[jeetee]

Filing one against MS3 is no use, as that branch is no longer in development (nor has it been for over a year).
And given that the plugin API for MS4 is still in flux, it can't hurt to enter one against it; assuming this issue is still the case in there and that the plugin is able to run at all.
Which it currently can't as dockable plugins are not supported in it yet.