Adding a marker in Rosegarden rename the previous one

[Vivien Taillandier]

Binary package hint: rosegarden

After opening the box to manage markers, I click add.
I double-click on the new entry, change the measure and the name. I apply the change and then the previous marker has been renamed to "new marker".

Version : 1:1.5.1-3ubuntu 1
Dist : Gutsy

[Ralph Janke (txwikinger)]

Thanks for submitting this report and helping to make Ubuntu better.

I have tried to reproduced this issue on hardy. I can see a behaviour that fits the description given, however, it seems to be correct behaviour. The previously first marker is pushed to be the second, and the new marker is the first (since it will initially be at the beginning of the song). When the details are filled in, it moves to the correct place within the markers.

I would like to close this report if this is ok. If not please explain what different behaviour should be expected.

Thanks again for the help.

[Vivien Taillandier (vivien)]

Thanks for your answer, but I still have a problem.

Here is to how to reproduce the issue (on hardy).
Create a new project.
Draw a three-measure staff.
Insert a marker at the first period and name it "Test".
Open the markers editor.
Insert a new marker at the third period and name it "Test 2".
Click on Test or Test 2 and add a new marker. At this point, you should have a new marker at the same time as Test or Test 2, named "New marker".
The bug happens when you change the value of the period (from 3 to 2 or 1 to 2) and rename the marker, like "Result".
The new marker is okay, but the marker you clicked on just before will be renamed to "new marker" instead of keeping the original name.

I hope I've correctly described the issue and you'll be able to reproduce it.

[Ralph Janke (txwikinger)]

I can confirm the behaviour as described in comment #2 on Hardy.

[Ted Felix (tedfelix)]

Tried reproducing this with the latest version of rg (upstream from svn). I could not. I think this has been fixed (probably during the qt4 upgrade a couple of years back). I believe this bug can be closed.