On my build of [e85854] the problem occurs randomly, regardless of
whether the playback pointer is inside or outside the active segment. I
thought it was related to whether the notes were before or after the
pointer but it's still random with respect to that. Also got one crash
which I can't recreate.
MatrixWidget::updatePointer() and NotationWidget::updatePointer() seem
very different and it wasn't clear to me how to modify the former to
call Panned::showPositionPointer(QPointF top, float height) instead of
Panned::showPositionPointer(float x) because matrix doesn't have an
analogue to NotationScene::getCursorCoordinates(). If you'd like me to
do an independent test please provide details. My apologies if I'm not
seeing something that should be obvious.
On 6/3/22 2:30 PM, Yves Guillemot wrote:
Indeed I don't see the problem when the pointer is outside the segment
and the modification of the update() call seems to fix the bug.
(I only quickly tested the current issue and didn't look for any
possible regression.)
Yves
Le 3 juin 2022 à 22H42 (+0200)
Philip Leishman <leish...@web.de> a écrit :
I have been experimenting a bit here.
I can only reproduce the error if the pointer position is within the
segment.
with the pointer position at the start of the composition try a
segment starting at bar 2. I do not get the error.
Move the pointer to bar 3 and create a segment from bar 2 to bar 4.
Now I get the error.
Looking into Panned.cpp:
There are 2 showPositionPointer routines. One is used by the notation
editor and one by the matrix editor.
The Notation editor version uses viewport()->update(). The matrix
editor version calls viewport()->update(newRect).
If I change to the viewport()->update() call the bug seems to
disappear !!!!
Don't ask me to explain this but maybe someone can confirm this
behavior.
Philip
_______________________________________________
Rosegarden-devel mailing list
Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel