int cylinderindex;
};
+/*
+ * Events are currently pretty meaningless. This is
+ * just based on the random data that libdivecomputer
+ * gives us. I'm not sure what a real "architected"
+ * event model would actually look like, but right
+ * now you can associate a list of events with a dive,
+ * and we'll do something about it.
+ */
+struct event {
+ struct event *next;
+ duration_t time;
+ int type, flags, value;
+ char name[];
+};
+
#define MAX_CYLINDERS (8)
struct dive {
depth_t visibility;
temperature_t airtemp, watertemp;
cylinder_t cylinder[MAX_CYLINDERS];
- double otu;
+ int otu;
+ struct event *events;
int samples, alloc_samples;
struct sample sample[];
};
extern void renumber_dives(int nr);
+extern void add_event(struct dive *dive, int time, int type, int flags, int value, const char *name);
+
/* UI related protopypes */
extern void init_ui(int argc, char **argv);
extern void dive_list_update_dives(void);
extern void flush_divelist(struct dive *dive);
-extern int open_import_file_dialog(char *filterpattern, char *filtertext,
- void(* parse_function)(char *));
#define DIVE_ERROR_PARSE 1
const char *weekday(int wday);