Evoral::Sequence: tweak DEBUG_TRACE messages during note removal

This commit is contained in:
Paul Davis 2025-10-31 12:30:48 -06:00
parent db44a58a54
commit 637f22508b

View file

@ -749,7 +749,7 @@ Sequence<Time>::remove_note_unlocked(const constNotePtr note)
bool erased = false;
bool id_matched = false;
DEBUG_TRACE (DEBUG::Sequence, string_compose ("%1 remove note #%2 %3 @ %4\n", this, note->id(), (int)note->note(), note->time()));
DEBUG_TRACE (DEBUG::Sequence, string_compose ("%1 remove note #%2 %3 @ %4 of %5\n", this, note->id(), (int)note->note(), note->time(), _notes.size()));
/* first try searching for the note using the time index, which is
* faster since the container is "indexed" by time. (technically, this
@ -794,10 +794,10 @@ Sequence<Time>::remove_note_unlocked(const constNotePtr note)
}
}
DEBUG_TRACE (DEBUG::Sequence, string_compose ("%1\ttime-based lookup did not find note #%2 %3 @ %4\n", this, note->id(), (int)note->note(), note->time()));
if (!erased) {
DEBUG_TRACE (DEBUG::Sequence, string_compose ("%1\ttime-based lookup did not find note #%2 %3 @ %4\n", this, note->id(), (int)note->note(), note->time()));
/* if the note's time property was changed in tandem with some
* other property as the next operation after it was added to
* the sequence, then at the point where we call this to undo