mirror of
https://github.com/subsurface/subsurface.git
synced 2025-02-19 22:16:15 +00:00
Fix selection logic when manually adding a dive
This was an interesting bug. When adding a dive that would end up in the middle of the dive list, the newest dive in the dive list would end up marked in the dive structure as selected - even though it wasn't visualized as selected by Qt. Bad things happen if the user then made changes to that dive without selecting something else first, for example by either editing the dive or doing things to it like removing it from or adding it to a trip. The same operation would also be applied to the newest dive in the dive list. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
This commit is contained in:
parent
b8823acef9
commit
4a04fc2a1b
2 changed files with 14 additions and 5 deletions
|
@ -189,13 +189,19 @@ void DiveListView::selectTrip(dive_trip_t *trip)
|
|||
|
||||
void DiveListView::unselectDives()
|
||||
{
|
||||
// make sure we don't try to redraw the dives during the selection change
|
||||
selected_dive = -1;
|
||||
amount_selected = 0;
|
||||
// clear the Qt selection
|
||||
selectionModel()->clearSelection();
|
||||
// clearSelection should emit selectionChanged() but sometimes that
|
||||
// appears not to happen
|
||||
// since we are unselecting all dives there is no need to use deselect_dive() - that
|
||||
// would only cause pointless churn
|
||||
int i;
|
||||
struct dive *dive;
|
||||
for_each_dive(i, dive) {
|
||||
deselect_dive(i);
|
||||
dive->selected = false;
|
||||
}
|
||||
}
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue