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

Many thanks for 4.12beta15 and the source code. Appreciated as always.

Some initial mostly 4.12beta15 specific feedback is below. It can be stated any changes would not adversely affect any existing functionality or user.

Separate ClearTrack and Clear2Follow buttons on Menu page are working correctly and self explanatorily when either a .gcc or .gpx or .kml has been loaded allowing independent separate clearing without affecting the other.

When 'edit t2f (add points)' has been selected on Map Screen Context Menu, and points added on the map screen, unless a .gpx or .kml Track2Follow has been loaded, on Menu screen there is no Clear2Follow button available. Tested in Windows CE 5 Emulated Environment. Not applicable to any Windows Mobile OS or device.

Recall buttons have been moved to the end of the menu. The latter part of post 2158 refers.

Pause functionality now allows the pause button to remain whilst GPS is switched off, whereupon pressing pause again to unpause switches GPS back on and logging resumes without Confirmation prompt.

Whether or not the separate issue, which is not to be conflated, has been resolved of when GPS is on but signal is lost whilst on pause, and then unpaused before signal is reacquired, whereupon the Confirmation prompt would reportedly appear in some circumstances when GPS lock is reacquired, will have to confirmed by the user that reported the issue as that issue could not be reproduced.

If 'Show 'Exit' after Stop' and 'Confirm 'Pause' and 'Stop' are enabled on Menu > Options > Main screen, when logging, if Stop is pressed, and then No on the Confirmation prompt, the Stop button incorrectly changes to the Exit button when it should remain as the Stop button as logging has not stopped. This is not a new issue, it was first noticed in 4.11 Final and has been awaiting compilation for quite some time as has a lot of feedback.

Text size change overall is an improvement making better use of the available screen space, and when implemented correctly and the intelligence that determines the size of font relative to screen size and other factors is further refined so that current issues with some text appearing off screen or overlapping other text / features is resolved, most if not all users will probably find the feature useful. The current issues are not Windows CE specific. As this is dynamic, and although the feature could be made optional, it is difficult to envisage at this stage a circumstance where a user would wish to disable this once working without issue.

Window CE Titlebar removal is working, and minimise, maximise, and full screen are correctly implemented and there no longer occurs switch from portrait to landscape orientation. On devices where the Taskbar is already disabled or otherwise not routinely displayed, essentially full screen is achieved and the display is the same as that enjoyed by Windows Mobile users. For devices that do show the taskbar, this is not currently handled, specific feedback on how to implement handling of Taskbar to follow in due course. Tested in Windows CE 5 Emulated Environment. Not applicable to any Windows Mobile OS or device.

It can be observed a glitch occurs on first run of 4.12beta15 when a previous version has been used after the 'Warning Unexpected EOF while reading.........' where the Taskbar in Windows Mobile remains visible. It does not recur again afterwards and appears to be caused by this warning message.

App maximized behaviour on Windows Mobile is otherwise unaffected and working as previously on screen. Some devices have manufacturer provided User Interface enhancements, such as HTC Sense and Samsung TouchWiz. These overlay the Windows Mobile UI and may interfere with its ordinary functions. HTC Sense does not however exhibit any issues. It can be readily determined if UI enhancement is causing an issue by disabling it. GCC can then be adapted accordingly as required.

The wording 'App maximized' would be better changed to 'App full screen' or just 'Full screen' it being inherently obvious it refers to the GCC application. 'App maximized' is neither technically accurate, descriptively accurate or therefore self explanatory or intuitive. 'App full screen' or just 'Full screen' are all those as has been previously detailed. This is a change of wording only in Context menu, not an actual change of functionality.

Map Screen configurable info values initial implementation provides a very good foundation upon which to build. Below are some amendments and refinements that are apparent from initial cursory testing:

Windows CE Context Menu on Map Screen lower 12% does not function properly. Context Menu appears correctly upon press and hold, but upon removing, Context Menu does not remain as it should. Tested in Windows CE 5 Emulated Environment. Not applicable to any Windows Mobile OS or device.

Display of the units (miles etc) could be in a smaller font size than that of the actual numerical value as overlapping can currently occur, particularly with three fields in use. Furthermore, the unit could be displayed underneath instead of alongside the numerical value, allowing perhaps four fields instead of three. Furthermore, fields need not be limited to three or four, larger screen devices could easily cater for more by stacking rows of fields.

The existing functionality could be expanded to include handling of the scale, tiles, and coordinates information on the map screen, allowing these to be selectively turned off.

The existing functionality could be expanded to include ability to switch on/off the selected information on the map screen at once.

Safeguard could be implemented to prevent selection of the same info value for more than one field. For instance, the same info value can be selected for all three fields currently.

Safeguard could be implemented to prevent selection of similar background and Map label colours being selected, similar to the existing 'Warning Fore and back color are too close together. Ignore setting' preventing the hidden / hard to see text effect when 'Clear Background' is selected.

'clear background' is not applied to the text when 'show names' is selected, this allows more map to be visible, however some users may however require the names to be visible having selected them, for the same reasons as the data, so this option could be provided.

'clear background' would be be better changed to alternative wording as the background when selected is not clear, i.e. transparent, it is the opposite, an opaque block colour. This is a change of wording only in Context menu, not an actual change of functionality. It could be changed to 'no map background' which would be descriptively accurate, self explanatory and naturally therefore more intuitive. Alternatively, 'show map background' could be used, which would require the switch to work opposite to as at present to reflect that wording, but would provide consistency with 'show names' and have the aforementioned advantages.

Further Windows CE specific feedback is awaiting compilation and will be provided in due course.

The mid part of post 2029 refers.

Further information to be added.

low.flying.pigs