regression with part resize #1167
Replies: 6 comments
-
Oops. My bad. Fixed regression at 23.05.2010 Should work although untested. I think that section doesn't even have any bearing Whenever an item's position changes, it is now important to change the mp (moving point) |
Beta Was this translation helpful? Give feedback.
-
No problem, I'm glad I'm not the only one introducing errors ;) ..oh well. I saw your fix, and this was actually what I tried, for parts it does not behave right (but avoids the crash which is good). I get now that CItems can be notes too so I can have a closer look with that in mind, got no time right now though. |
Beta Was this translation helpful? Give feedback.
-
Finally had a second look at this. |
Beta Was this translation helpful? Give feedback.
-
Hi. Looking at it now. Which "next step" do you mean? |
Beta Was this translation helpful? Give feedback.
-
The PartCanvas::resizeItem(CItem* i, bool noSnap, bool ctrl) |
Beta Was this translation helpful? Give feedback.
-
OK I removed it. |
Beta Was this translation helpful? Give feedback.
-
I noticed it crashed when I tried to resize a part to the left recently.
I of course blamed myself due to having worked on this but the issue happened elsewhere.
This snippet from canvas.cpp
case DRAG_RESIZE:
if (curItem) {
if(resizeDirection == MusECore::ResizeDirection::RESIZE_TO_THE_LEFT) {
if (!supportsMultipleResize) {
QPoint rpos = QPoint(raster(pos).x(), curItem->y());
resizeToTheLeft(rpos);
curItem->move(start);
// Even though we only move the primary position here,
// set the mp as well.
//newCItem->setMp(newCItem->pos());
}
If I comment out that last newItem line it starts to work (since newItem is a null pointer).
I figured maybe it was supposed to be curItem but that behaves really wrong.
Has anyone touched this recently and know what it's supposed to do?
Judging by the comment it feels unimportant and my test works fine without it...
Beta Was this translation helpful? Give feedback.
All reactions