II do not want to kill your optimizm but I am sure Tim will have an explanation wha he will not do this.
Also he field "arrival tim" is nuts.
My minimum expectation would be, as SD is incapable to automatic recognize off block /on block that I can put in Daperture time and arrival time and so that PIC time is automatic calculated.
But as Tim pointed out on several occasions "we at SD do not see a need for a logbook and we do do not implement tis feature"
followed by, we do not implement a feature just others have i, so if you need this SD is maybe not the right application for you" ;-)
and no, they will also not implement a CSV import because first there is no need and 2. as said, SD never intended to have a logbook feature .......
Does this sound frustratedß ABSOLUTELY! I had used air navigation pro for almost 9 years nad would do if they would not have such a catastrophic support. But beside tis it was pretty much good. Logbook feature was an ease to use, automatic very precise Off Block/on block times also did record even touch and go precise. As the logbook is stored in an SQL format, it was easy to import/export. Also EVERY field was editable. Because it should be! SD pretty much shows that the logbook can be faulty when the software itself takes control. You end up with wrong records which later are hard to change correct resulting in wrong times and landings.
Easy to do in ANP, pain in the A... in SD
But maybe sooner r later Tim can overcome his personal point of view and can react on customer needs......paying the show......