mirror of
https://github.com/subsurface/subsurface.git
synced 2025-02-19 22:16:15 +00:00
Fix renumbering of dives
The implementation in commit 182fe790c9
("Add ability to undo
renumbering of dives") looks perfectly reasonable, but it depends on an
implementation detail: it assumes that the keys of the QMap are returned
in the same order in which they were placed there. Which apparently isn't
the case for some version of Qt.
With this commit we simply remember both the old and the new number for
each dive and therefore the order in which they are processed doesn't
matter.
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
This commit is contained in:
parent
a524c01c3f
commit
8d05c71ca2
3 changed files with 12 additions and 12 deletions
|
@ -143,14 +143,16 @@ void RenumberDialog::renumberOnlySelected(bool selected)
|
|||
void RenumberDialog::buttonClicked(QAbstractButton *button)
|
||||
{
|
||||
if (ui.buttonBox->buttonRole(button) == QDialogButtonBox::AcceptRole) {
|
||||
QMap<int,int> renumberedDives;
|
||||
// we remember a map from dive uuid to a pair of old number / new number
|
||||
QMap<int,QPair<int, int> > renumberedDives;
|
||||
int i;
|
||||
int newNr = ui.spinBox->value();
|
||||
struct dive *dive = NULL;
|
||||
for_each_dive (i, dive) {
|
||||
if (!selectedOnly || dive->selected)
|
||||
renumberedDives.insert(dive->id, dive->number);
|
||||
renumberedDives.insert(dive->id, QPair<int,int>(dive->number, newNr++));
|
||||
}
|
||||
UndoRenumberDives *undoCommand = new UndoRenumberDives(renumberedDives, ui.spinBox->value());
|
||||
UndoRenumberDives *undoCommand = new UndoRenumberDives(renumberedDives);
|
||||
MainWindow::instance()->undoStack->push(undoCommand);
|
||||
}
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue