undo: split out EventBase class

All event-based commands will work on a dive computer and
need to replot the profile, etc. Therefore, in analogy to
the dive-list commands create a base class with two virtual
functions undoit() and redoit() that must be defined in the
derived classes that do the actual work.

Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>

1 files changed, 14 insertions, 5 deletions

diff --git a/commands/command_event.h b/commands/command_event.h
index 8cceaeb25..a674e258b 100644
--- a/commands/command_event.h
+++ b/commands/command_event.h
@@ -16,19 +16,28 @@ namespace Command {
 // Therefore, the undo commands work on events as they do with dives: using
 // owning pointers. See comments in command_base.h
 
-class AddEventBase : public Base {
-public:
-	AddEventBase(struct dive *d, int dcNr, struct event *ev); // Takes ownership of event!
-private:
-	bool workToBeDone() override;
+class EventBase : public Base {
+protected:
+	EventBase(struct dive *d, int dcNr);
 	void undo() override;
 	void redo() override;
+	virtual void redoit() = 0;
+	virtual void undoit() = 0;
 
 	// Note: we store dive and the divecomputer-number instead of a pointer to the divecomputer.
 	// Since one divecomputer is integrated into the dive structure, pointers to divecomputers
 	// are probably not stable.
 	struct dive *d;
 	int dcNr;
+};
+
+class AddEventBase : public EventBase {
+public:
+	AddEventBase(struct dive *d, int dcNr, struct event *ev); // Takes ownership of event!
+private:
+	bool workToBeDone() override;
+	void undoit() override;
+	void redoit() override;
 
 	OwningEventPtr eventToAdd;	// for redo
 	event *eventToRemove;		// for undo