Possible bug: Incorrect bar numbers in comments list

When opening a project;

the comment does not span any bars. When renaming the comment

the number is correct.

I can confirm that renaming a comment looses the shown bars span (and only the bar number where the comment is positioned is shown), while replying to a comment, maintains the bars span.

I’m curious when a span is actually valid. A comment might have a span for a tied note, but it’s a bit of a stretch. I’d rather just have the single bar number.

So how do these spans emerge?

What would be nice to have is the “beat” too, like “#:3” or “#:3.5”. Perhaps in a future version?

It may just be an unintended consequence of creating a Comment with a selected region that covers more than one bar. If you subsequently interact with the Comment, e.g. edit it – then it reverts to a single bar/point.

TBH, I never noticed that ranges could be shown; and even so, I wouldn’t read too much into it.

1 Like

Yes! You are correct as usual. If I selected 2+ bars it does add a span

It could have some value if one wants to comment on a longer section.

Anyhow, now I know how they emerged. The question is if they should not remain as a span if edited, for those that use the span-feature.