On 1 Bře, 18:48, Lluis Gesa <
lluis.g...@gmail.com> wrote:
> > Sorry, the bug appears when you create a track and try to load it once
> > again (not when you try to load certain track twice, that works fine).
> > The phone says "application error", when I ask for more details, it
> > says "Null Pointer java/lang/NullPointerException".
>
> I'm trying to imagine the sequence... you create a new track, and just
> after, do you try to load it? without data logged or with it ?
--> yes, I create a new track and try to load with Load option just
after (with no data). I know it is a nonsense because the app self-
loads recently created track, but I happened to had started using
eGPSTrack before I read the manual and I thought it was necessary to
create AND load a track. No matter if GPS is online or offline.
>
> What about highspeed feature, have you considered? I am not keen on
>
> > programming, but it doesn't look like a great deal, what do you think?
> > Thanks :)
>
> Is not complex to store speed together with data, I will try to send you a
> test-version with it next week.
--> thank you very much. Do you plan to add an option to see the
maximum speed directly in the application, or will the speed
information just be logged as the GPS coordinates in the *.log file?
both possibilites are fine, the second case just calls for a PC post-
processing to get a sensemaking info.
>
> one note about you suggestions:
>
> d) multiple track logging. Sometimes we also may appreciate logging
>
> > the GPS data into more than just one track simultaneously.
>
> Can you describe an example scenario?
--> in the same way you use split timing on a stopwatch. Somebody may
want to have one log (especially the statistic information) valid for
the whole day, and another log for just one ride (downhill skiing -
the overall distance skied through the day is as important as the
distance skied during last run, and so are the altitude changes and
calculated average speeds). Currently you have to create a new track
for the run you wish to measure separately, but logging of the
previous track is terminated. If you wish to preserve information
undistorted by next runs, you cannot continue to write data in neither
of the tracks - you have to create a new one, which results in a mess
of files and is quite uncomfortable. I've had in my mind some more
scenarios, but can't remember. I will write later if I recollect.
I hope I'm not annoying you too much with my complaints, so as a
conclusion - eGPSTrack is already really a fine program and I wish you
good luck and a lot of patience to further development!
Adam
>
> Lluís.