Create a 'remove_event' function that removes an event.

The logic of removing the event was in the UI, and this makes
the code harder to test because we need to take into account
also the events that the interface is receiving, instead of
only relying on the algorithm to test.

so, now it lives in dive.h/.c and a unittest is easyer to make.

Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>

1 files changed, 11 insertions, 0 deletions

diff --git a/dive.c b/dive.c
index d9943c23f..7e211f163 100644
--- a/dive.c
+++ b/dive.c
@@ -65,6 +65,17 @@ void add_event(struct divecomputer *dc, int time, int type, int flags, int value
 	remember_event(name);
 }
 
+void remove_event(struct event* event)
+{
+	struct event **ep = &current_dc->events;
+	while (ep && *ep != event)
+		ep = &(*ep)->next;
+	if (ep) {
+		*ep = event->next;
+		free(event);
+	}
+}
+
 int get_pressure_units(unsigned int mb, const char **units)
 {
 	int pressure;