I'm in the same boat and last week I started working on adding an additional field to both subsurface and libdivecomputer (I called it voted PO2). I managed to get the import and display of it working before I got interrupted by other stuff. It has subsequently occurred to me that this may not be the best approach.
I'll have a look at it again and try and come up with a better way. Aaron On Sun, Jun 17, 2018, 11:53 Davide DB <dbdav...@gmail.com> wrote: > On Thu, Jun 14, 2018, 15:34 Long, Martin <mar...@longhome.co.uk> wrote: > >> I'm in agreement with Davide that any interim solution we can get running >> is better than the way it is working now. It's a regression, and tbh if >> there isn't an interim solution then it ought to be reverted to the old >> behaviour. At the moment I'm having to use Shearwater desktop for reviewing >> all my logs. >> > > I had to stop using Subsurface for the time being. First time in so many > years. > > If the bug will be solved I would have to transfer and compile from > scratch more than 60 dives (until now). I don't know if I will have the > time or will to do all this work and frankly speaking I'm tired to be > always a minority. > > Farewell my friends. It has been a nice journey. Thank you all for the > amazing work. > >> > > davide@mobile > > > >> _______________________________________________ > subsurface mailing list > subsurface@subsurface-divelog.org > http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface >
_______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
