[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello Blaustein / Klaus,

Thank you for your prompt attention. In response to your comments:

24 Hour clock is displayed in hh:mm format. 12 Hour clock is displayed as hh:mm format. Both formats would use the same amount of space on the display. Your response is not therefore understood.

Windows Mobile will continue to run GCC as it does now as long as the hardware device itself continues working, can be fixed and / or replacement new or used obtained. Lifetime is not therefore strictly limited. Windows Mobile devices with an internal compass are not new. The HTC HD2 released in 2009 is one such example of very capable and versatile Windows Mobile device (which can also run Android, and / or dual boot both). Hardware compass is a feature implemented with GPS Mod Driver which does work in GCC. However, finding the optimal GPS Mod Driver configuration so everything works as desired and is usable requires futher testing.

http://xdaforums.com/showthread.php?t=571266

Hardware compass is a feature that I still think GCC would benefit from incorporating directly for the reasons previously detailed.

That is how it should work. The point is it doesnt on WM 6.5 on the HTC HD2 when 'keep touch on while backlight off' is selected, and then 'backlight' is pressed, the only way to then reactivate the screen is to press the power button.

A summary screen in the instance where the incorrect .gcc is selected is actually less clicks

Current - From Main Screen having selected incorrectly:

Menu > File/Export > Select gcc > Load (4 clicks)

Proposed - From File/Export Summary having selected incorrectly:

Cancel > Select gcc > Load (3 clicks)

This could be further simplified by a double click on the selected .gcc functioning as the command to load (1 click, 1 double click)

It is implemented. However, I have never found this particularly usable due to the way in which it is implemented and the presentation.

If there are to be no options I have to carefully consider this whilst carrying out futher testing.

There is another issue that seems to maybe stem from the 4096 point restriction. On large tracks, as points are being removed, the track does not always closely fit to the actual route. Straight lines are drawn between points resulting in things like tracks where there is no actual road / route through open land, buildings, built up areas etc. This is quite apparent when viewed over the map. Perhaps the fix will address this also.

What is the purpose of the 4096 point limitations in T2F, GPX and KML export features and why was it / is it still necessary anyway?

The link below does not really explain other that it was an arbitary value chosen at the time.

http://xdaforums.com/showpost.php?p=3484539&postcount=608

GCC has no issues handling the number of points in a large .gcc, so I am bemused as to why a limitation exists / is necessary for T2F. I am wondering how useful T2F will be for large tracks if this cannot be overcome.

That would be a good solution for audio waypoints. It seens to me somewhat odd the audio waypoints cannot be played within GCC on a T2F. What was the intention here?

Detailed within Help, section 7 Options in the Context menu "Main page" area. "You can switch on "beep on start/stop""

Apologies. My mistake.

Again, apologies. My mistake. However, I do still think an auto reset as detailed previously would be useful.

It is selected. Volume is at max. Other sounds are heard as previously detailed. Perhaps it may be trivial. It is however a feature that has been implemented in GCC which I have tested and found not on Windows Mobile 6.5 on the HTC HD2 (was working on WM 2003 SE). Hence it being reported. The fact it was implemented suggests it was of some usefulness to some users.

That is exactly what happend, which I had not realised. At least this has highlighted a further improvement.

Presumably you have never had or heard about any of the issues reported that are subsequently fixed. We have already previously discussed the fact the majority of users do not provide any feedback whatsoever in any event and that little if anything can be inferred from that you have not had or heard about an issue before. I will continue to see if I can narrow down the circumstance in which this occurs as detailed previously. Regarding user feedback, perhaps a prompt once in a while when closing GCC would encourage interaction and motivate some to be forthcoming with feedback for the benefit of all.

I would be very interested to see the to do list if it could be posted.

I look forward to testing and using the beta and thank you for your continued support and developement.

low.flying.pigs