mirror of
https://github.com/subsurface/subsurface.git
synced 2024-11-28 21:20:19 +00:00
29b242c703
This data structure was quite fragile and made 'undo' when editing rather hard to implement. So instead I decided to turn this into a QMultiMap which seemed like the ideal data structure for it. This map holds all the dive computer related data indexed by the model. As QMultiMap it allows multiple entries per key (model string) and disambiguates between them with the deviceId. This commit turned out much larger than I wanted. But I didn't manage to find a clean way to break it up and make the pieces make sense. So this brings back the Ok / Cancel button for the dive computer edit dialog. And it makes those two buttons actually do the right thing (which is what started this whole process). For this to work we simply copy the map to a working copy and do all edits on that one - and then copy that over the 'real' map when we accept the changes. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
30 lines
619 B
C++
30 lines
619 B
C++
#ifndef DIVECOMPUTERMANAGEMENTDIALOG_H
|
|
#define DIVECOMPUTERMANAGEMENTDIALOG_H
|
|
#include <QDialog>
|
|
|
|
class QModelIndex;
|
|
class DiveComputerModel;
|
|
namespace Ui{
|
|
class DiveComputerManagementDialog;
|
|
};
|
|
|
|
class DiveComputerManagementDialog : public QDialog{
|
|
Q_OBJECT
|
|
|
|
public:
|
|
static DiveComputerManagementDialog *instance();
|
|
void update();
|
|
void init();
|
|
|
|
public slots:
|
|
void tryRemove(const QModelIndex& index);
|
|
void accept();
|
|
void reject();
|
|
|
|
private:
|
|
explicit DiveComputerManagementDialog(QWidget* parent = 0, Qt::WindowFlags f = 0);
|
|
Ui::DiveComputerManagementDialog *ui;
|
|
DiveComputerModel *model;
|
|
};
|
|
|
|
#endif
|