mirror of
https://github.com/subsurface/subsurface.git
synced 2025-02-19 22:16:15 +00:00
map: don't explicitly reload the map from the mainwindow
The map listens to the reset signal by itself. This avoids double reload of the map on open/close. Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
This commit is contained in:
parent
fbb737e85b
commit
3abb82bfd5
2 changed files with 1 additions and 7 deletions
|
@ -120,7 +120,7 @@ void MapWidget::divesChanged(const QVector<dive *> &, DiveField field)
|
|||
// Sadly, for reasons out of our control, we can't use a normal singleton for the
|
||||
// map widget: In a standard singleton, the object is freed after main() exits.
|
||||
// However, if there is an animation running (map zooming), the thread is
|
||||
// terminated, when the QApplication object is destroyed, which is before main()
|
||||
// terminated when the QApplication object is destroyed, which is before main()
|
||||
// exits. The thread has a QQmlAnimationTimer that is freed. However, the map widget
|
||||
// then tries to free the object itself, leading to a crash. Clearly, a bug in
|
||||
// the QML MapWidget / QtQuick ecosystem.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue