mirror of
https://github.com/subsurface/subsurface.git
synced 2025-02-19 22:16:15 +00:00
Cleanup: remove selectionChanged logic from dive-list commands
Since all commands now fully reset the selection, there is no point in keeping track of whether the selection changed on addition or removal of dives. This can be done in the function that sets the selection. Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
This commit is contained in:
parent
e1abf9485c
commit
4716c82032
5 changed files with 30 additions and 68 deletions
|
@ -99,8 +99,7 @@ void EditBase<T>::undo()
|
|||
DiveField id = fieldId();
|
||||
emit diveListNotifier.divesChanged(QVector<dive *>::fromStdVector(dives), id);
|
||||
|
||||
if (setSelection(selectedDives, current))
|
||||
emit diveListNotifier.selectionChanged(); // If the selection changed -> tell the frontend
|
||||
setSelection(selectedDives, current);
|
||||
}
|
||||
|
||||
// We have to manually instantiate the constructors of the EditBase class,
|
||||
|
@ -539,8 +538,7 @@ void EditTagsBase::undo()
|
|||
DiveField id = fieldId();
|
||||
emit diveListNotifier.divesChanged(QVector<dive *>::fromStdVector(dives), id);
|
||||
|
||||
if (setSelection(selectedDives, current))
|
||||
emit diveListNotifier.selectionChanged(); // If the selection changed -> tell the frontend
|
||||
setSelection(selectedDives, current);
|
||||
}
|
||||
|
||||
// Undo and redo do the same as just the stored value is exchanged
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue