THX + improvement proposals :)

2 views
Skip to first unread message

Killer

unread,
Feb 28, 2009, 11:35:32 AM2/28/09
to eGPSTrack
Hi there,

first of all, thanks a lot for this application!!! I really appreciate
it because it is easy to get used to and it works pretty fine. Anyway,
as with every sweet little babe, there are things that call for
refinement and I hope not to offend you by providing some of them :)

Tested on Nokia 5310 (series 40) + Nokia LD-3W bluetooth GPS module.

bugs:

a) when a track has already been loaded, an attempt to load it once
again results into an application crash.
b) help content sometimes goes out of the screen (only a part of a
line is visible)

Haven't noticed any more, which means the program's pretty good :)

suggested possible refinements:

a) Elevation map scrolling and scaling. I think that almost nobody
goes from 0 mts to the highest achieved point in a track, so there is
no reason to fix the lowest altitude in the graph. Scrolling in time
(left to right) and scaling (up-down direction) would be very nice!

b) High speed logging. A speed graph is not necessary, but since I am
using the application mainly for skiing, it would be very useful to
have maximal speed column in Statistics or anywhere else. It's pretty
hard to keep those tiny numbers in sight while going down at 80 km/h
(but the same applies to using eGPSTrack while riding a bike, skating
etc..) :) which is connected with...

c) GPS page optimalization. If possibly the units of all the values
were indepedent to have been set (e.g. altitude in meters, speed in km/
h and other parameters in Statistics page), it would be awesome. Also
adjustable font size and show/hide feature of individual parameters
may turn into a powerful outdoor tool.

d) multiple track logging. Sometimes we also may appreciate logging
the GPS data into more than just one track simultaneously.

Anyway, those are just small tips that may or may not be reflected in
future versions, depending on your sentiment. I just pray for that
highspeed logging :-D

Cheers,

Adam

Lluis Gesa

unread,
Feb 28, 2009, 6:53:52 PM2/28/09
to egps...@googlegroups.com
Thanks for your notes. About bugs:


a) when a track has already been loaded, an attempt to load it once
again results into an application crash.

Is showed any message when eGPSTrack crashes?


b) help content sometimes goes out of the screen (only a part of a
line is visible)

Your are right, I need to improve help on screen. I need to add some scroll system and better margin detection.

Killer

unread,
Mar 1, 2009, 10:58:09 AM3/1/09
to eGPSTrack
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".

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 :)

Adam
> > Adam- Skrýt citovaný text -
>
> - Zobrazit citovaný text -

Lluis Gesa

unread,
Mar 1, 2009, 12:48:26 PM3/1/09
to egps...@googlegroups.com
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 ?


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.

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?

Lluís.

Killer

unread,
Mar 2, 2009, 7:23:07 PM3/2/09
to eGPSTrack


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.
Reply all
Reply to author
Forward
0 new messages