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

In brief response to your comments:

GCC requires a touch screen Windows Mobile device to function. The term 'gesture' is used in reference to touch screen commands as detailed the original feedback.

In the original feedback, zoom limits work in conjunction with continous zoom. Curtailed functionality within the realms of sensible, proportianate and usable practicality, does not constitute a violation or limitation of any 'freedoms'. Your response again does not address the actual question "What is the purpose of these extremes?"

In the original feedback zoom enhancement works in conjunction with zoom limits, and compliments continous scroll. It is sensible as detailed therein.

Yes, there was thought in detail. No, there was no proposal. There was however an observational question.

Nearest point available clearly and obviously means nearest usable point available as was clarified. The question remains why always 100m ahead and not whatever nearest usable point is available?

Thank you for the explanation.

The unfortunate fact of the matter is that much 'very valuable information' is undoubtedly lost due to the previously detailed reasons that dissuades users from contribution in the first instance to the considerable detriment of the GCC project.

The unfortunate reality is someone would probably be unable to refrain from stating thier objection to 'audio-candy fancy stuff' similar to previous objections to 'eye-candy fancy stuff' and objection to 'discussion in a discussion forum'. Fortunately, or unfortunately, that for now is not an issue because the Jenny voice cannot be legitimately distributed within GCC, at least for the time being.

Jenny voice was only 'proof of concept' created as detailed in the Private Message. There exists a clear difference between collaborative development for testing purposes and personal usage which is permitted, and mass distribution which is not generally permitted. You should refer to the 'Terms of Use' and seek specific consents accordingly if you wish to distribute. The Kimberly voice has a similar issue, as will probably any voice created in a similar manner. As previously detailed, the conduct of ElfKaa has ruined any immediate prospect of a freely and readily distributable voice I was in position to have provided for the benefit of all to further the GCC project, hence the creation of the 'proof of concept' in the manner it was instead, and the current situation. I will nonetheless persevere and continue to explore options. Like all feedback and contribution I make, it is done on the basis of the continued development and well being of the project overall. In this instance my own usage of Track to Follow is such that currently viewing the map when necessary suffices, and I have no usage or need of any voice, let alone any need to create one, but I do what I can anyway.

The problem is as detailed in the original feedback. The cause of the issue is presently undetermined. If any progres is made, I will provide details accordingly.

Thank you for the explanation. There does seem scope with suitable modification for verify login to also function as a simple connectivity check by using the stored hash if present, if a password has not been manually entered.

If the option to freely set live logging intervals in 1 minute intervals is implemented, if the user had enabled live logging, the existing selected 'preset interval' could be detected and automatically applied if it was an actual issue, or the 'GCC - Important News' or similar could be made to appear when first run alerting the user to set their live logging interval if necessary.

Users with the ability to do so may well select an interval that actually matches their requirement, rather than continue to accept the nearest available inflexible compromise previously forced upon them, which could be considered as 'limiting freedom'.

All that is required and was envisaged is an up/down minute button selection, similar to that already used for 'GPX time adjustment, hours' on the Kml/Gpx page in Options. Probably selection within the existing range of 1 minute to 60 minutes is adequate, more than 60 minutes not being particularly 'live logging'. Maybe for now an inital 30 second option can be dropped for ease of implementation if necessary. As it is unecessary, drop down lists and appending anything to them probably would be as you state 'totally foolish'.

When implemented, name and description for .gcc files will be most useful indeed.

Facility for automatic insertion of coordinates from location selected on map, for similar reasons any coordinates would be entered in to LatLon. There appears no way to do this currently.

Thank you for the explanation.

Unfortunately your 'not liking' additional buttons limits scope to the existing buttons and the only foreseeable poor choice available working within that limitation and without implementing other features or doing other things.

Regarding the pressed image on the menu buttons in the menu, an observation is that at least on a fast device, it is generally not seen as there is little to no delay between pressing the button and function being actioned if it is available. On the buttons at the bottom of the screen however, it is always seen albeit often fleetingly for the same reason.

Unavailable buttons could be displayed using the existing unpressed image, but disabled, and made discernible with the text underneath the buton stating 'Unavailable' instead of [button function]. This retains the order of the buttons, and provides a simplistic solution.

Since the functionality was worthy of developmental time and effort which has already been expended and indeed the functionality actually created, kindly reinsert the functionality, selectable under options, default off as detailed previously.

ElfKaa has caused more than enough detriment already to the GCC project as detailed previously. ElfKaa's discredited comments are irrelevant. ElfKaa or anyone else that does not require the functionality would not be affected as detailed previously. Those that do require it, or would use it were it available, and the GCC project overall, should not suffer further detriment due to ElfKaa.

low.flying.pigs