c8389a5644
Since struct divecomputer is now fully C++ (i.e. cleans up after itself), we can simply turn the list of divecomputers into an std::vector<>. This makes the code quite a bit simpler, because the first divecomputer was actually a subobject. Yes, this makes the common case of a single divecomputer a little bit less efficient, but it really shouldn't matter. If it does, we can still write a special std::vector<>- like container that keeps the first element inline. This change makes pointers-to-divecomputers not stable. So always access the divecomputer via its index. As far as I can tell, most of the code already does this. Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
This directory contains shared UI backend code shared between the desktop version and the mobile version. The backend code sits between the actual functionality, which are implemented in core and qt-models, and the UI/QML which are implemented in desktop-widgets and mobile-widgets. The idea of backend is not to duplicate code, and at the same time limit the UI and QML to only deal with real GUI. The first implementations for backend are "export" and "diveplanner".