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

In brief response to your comments, and others arising:

Gesture Limits:

My understanding is that while Windows Mobile determines the gestures available overall, applications control how they make use of them and can limit gestures that originate within the application to within the application, or further still within defined areas of application.

Zoom Limits:

Your response does not address the actual question "What is the purpose of these extremes?"

If there exists no purpose, and one has not been given, nor can it be foreseen hence the question in the first instance, sensible limitation as described remains sensible. Your comment "in real life you should never need more than 10" appears to confirm that.

Continuous Zoom:

Your response again does not address the actual feedback. If continuous scroll is a good idea, then continuous zoom would seem so also, even if it is the bare minimum press and hold without further functionality as described.

100m ahead of T2F:

Using whatever nearest, usable, point is available in a T2F instead of always 100m ahead will presumably result in improved navigation? There was nothing in your response suggesting otherwise.

Miles for long distances:

In brief, with all due respect, the same could be said back to you. If a user selects a unit of measurement, it should be consistent throughout the application. UK and USA do not use kilometer for road distance measurement, nor are they likely to convert at any time in the forseable future. Nor does any other software have any issues in this regard.

Line to T2F:

If intentional, given direction and distance are shown when neither, or only one of current location or nearest part of the track are on screen, what is the purpose of the feature not showing direction and distance when current location and nearest part of the track are both on the screen together?

Change of line colour:

This is not observed with every T2F. There may be other circumstances in which it occurs, but it is observable as follows:

With the nearest point on the track some distance from the current location, the line is visible.

At the track end of the line, at a suitable zoom level to see the both the line and Start/Finnish way points on screen together, the line usually changes colour from that selected in options, map screen* to black, when the way points first appear on screen. When the way points move off screen, the line changes colour back again.

* Except when behaviour is different:

If black is selected, the line changing to black is not observable, if it occurs.

If [colour A] is selected, line is actually [colour B], changing to black and vice versa.

A - B

Grey - White

Brown - Red

Violet - Grey

This can be tested using the attached zipped .gpx file and remains as at 4.11 beta 6.

Female Voice:

Some progress was made with an actual human female voice. Unfortunately ElfKaa annoyed her to such an extent she has since refused further usage of her Samsung I8000 Omnia II and further recording or usage of her voice for GCC. I had considered asking again or others, however, given the apparent attitude of some 'contributors' and that experience, it is probably a 'totally foolish idea' to involve anyone else or further risk straining friendships or relationships.

Regarding the existing Jenny voice: 'five hundred' will be fixed.

Another voice, Kimberly, will be ready shortly.

Live Logging:

'Message from [insert user name] [insert time elapsed since message] GpsCC'

'[insert user name]'s Position | Last Update: 01/01/0001'

Before doing so, how have you determined these to be issues with Crossing Ways? I will contact Crossing Ways regarding this if needs be. GCC must be sending 'GpsCC' for Crossings Ways to display?

90 - Could not establish a connection to the server!

What should server URL be if not as pre entered? http://www.crossingways.com

Log in works fine. Live logging works fine. Problem remains.

Upload after Stop: How about redefining the checkbox to: "Create and upload GPX file after Stop"

If I understand correctly, replacing the existing 'Upload GPX file (after saving)'. Fine, if you wish to implement by that method.

Verify Login:

Since GCC does use the stored password without issue for live logging, there seems little or no reason it cannot be used to verify login, providing a quick and easy connectivity check. It seems any issues are due to how the verify log in feature is implemented.

Live Logging Interval:

Option to freely set this in 1 minute intervals instead of the current inflexible presets would be useful. An initial 30 second option has its uses for some applications.

File Name & Description:

It would be more user friendly if the context menu appeared by pressing and holding on a file in the list in the File/Export feature.

With a minor change to the .gcc format, name and description could be saved?

Input LatLon:

How? It does not seem to enter the coordinates in to LatLon?

Altitude Enhancement:

The further feedback to follow when compiled expands on this area, including slope.

Menu Screen - Rearrange Buttons:

The proposal was very thoroughly considered. It makes more sense than the existing arrangement.

Other users do have preferences and feedback and it would be valuable if more users in general would participate. As you know I have gladly submitted feedback for some who want to contribute but not directly. Unfortunately the issue persists of users being discouraged from participation. Some 'contributors' such as ElfKaa insist on making comments such as "Totally foolish idea". As has been extensively covered now in previous posts, this discourages user participation the first instance, and even usage of GCC at all, to the considerable detriment of the GCC project. The cumulative lasting incalculable damage of such conduct by ElfKaa for example to the project vastly out ways any comparatively minimal trivial benefit of any more positive and productive contribution made, which pales in to insignificance in comparison.

I would reduce clutter and relocate the Recall buttons for the reasons given. Your response does not detail your reasons.

The term 'greyed out' was used in reference to the computing term. No new buttons are necessarily required, there already existing two images for each button, unpressed, and pressed. If the buttons are not going to be hidden as described, currently unavailable buttons need only be discernable from those that are available. An obvious solution is instead of using the unpressed image for all initially, it is used only for those that are available. Unavailable buttons use the pressed image '[filename]_p.jpg' making them discernable, and when actually pressed, nothing happens.

Exit Button:

The proposal is not 'totally foolish'. ElfKaa's 'totally foolish' comment is 'totally foolish' and detrimental to the GCC project as detailed above.

The proposal is in fact well thought out and carefully considered and would not be proposed in the first instance were it not. It stems from a collaboration of users including myself that introduced GCC to the group, that use GCC on dedicated devices. Like any feature can be, it need not effect any user that does not require the functionality, being selectable within options and off by default. AE Button Plus is unnecessary and indeed incapable of achieving what is proposed. There is no need for any external software in the first instance when the proposal is completely achievable within GCC. There is no need to use hardware buttons when it can be done on screen. There is no reason why the exit button should be accidentally selected more than any other, and no reason why an optional 'Exit?' and 'Shutdown?' confirmation prompts cannot be provided. There will be no app close button in top right corner when GCC ultimately runs full screen without the taskbar, as other applications manage without issue. There are further reasons, the aforementioned will suffice for now.

low.flying.pigs