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

Many thanks for 4.12beta17, 4.12beta18, and the source code for the latter. Appreciated as always.

I am currently away and without access to my usual facilities, but here are some observations and initial feedback from cursory testing of 4.12beta18:

Readme.htm / Readme.txt: (Tested Windows Mobile 6.5 only)

Where Internet Explorer Mobile is installed on device and also the default browser, Readme.htm is displayed within GCC correctly.

Where Internet Explorer Mobile is installed on device but not the default browser, Readme.txt is displayed within GCC. This could be improved so that Readme.htm is still displayed in this circumstance, perhaps by checking for iexplorer.exe in \Windows

Where Internet Explorer Mobile is not installed on the device: Currently unable to test without access to facilities. However, most, if not all Windows Mobile devices have Internet Explorer. For Windows CE, either by checking for iexplorer.exe in \Windows or using OS detection, Readme.txt can be enforced.

Regarding the Readme.txt file and TextBox, the inherent limitations of 64Kb file size limit, no formatting and no hyperlinks are not applicable if Readme.rtf were used in conjunction with RichTextBox. This would allow for a larger file, with text formatting and hyperlinks (in the RichTextBox when correctly implemented). However, devices that do not have Internet Explorer Mobile typically do not have data connectivity either. Hyperlinks may not therefore be important but Readme.rtf could in all other respects be identical to Readme.htm and this would represent a relatively elegant solution.

Map Screen Info Fields:

Fields 2 and 3 incorrectly now apply their settings to Field 1.

Map Screen Auto Hide / Unhide Buttons:

'autohide buttons' should be renamed 'auto hide buttons'. autohide is not a word, auto and hide are two separate words.

When 'autohide buttons' is selected, upon entering Map screen, instead of buttons being immediately hidden which is not necessarily logical or intuitive (the wording 'auto hidden buttons' would be in that instance) or what the user necessarily actually requires, the buttons could optionally time out after short period of non usage. This could also apply after button usage. This would be consistent with the terminology 'auto hide buttons'.

The time out after which buttons auto hide could be user configurable, a range of 0 - 10 seconds perhaps (where zero is immediately hidden, timed out after 0 seconds, or up to 10 seconds before time out). The buttons are therefore available if required upon entering Map screen for immediate usage, allowing zooming as required without unnecessary tap, remaining available until a user has actually finished with their use, and then auto hide.

An additional feature labelled 'autohidden buttons' could immediately hide the buttons on the Map screen as that terminology logically and intuitively indicates.

The above is standard functionality and feature in other GPS mapping applications. It inherently caters for the needs of all users in this regard, and offers complete flexibility and functionality.

Unhiding of buttons could be limited to taps in the ordinary button area, leaving taps on the rest of the Map screen free for implementation of future functionality. Firstly, to actually use the buttons requires tap in the button area anyway. Secondly, it is easier to tap twice in the button area, than some other random place on the map screen and then move to button area. Thirdly, taps elsewhere could be better used more productively and gainfully for other purposes. Fourthly, prior to implementation of button hiding functionality there were no issues whatsoever with a user using the button area for button functions and no other. Consequently, no apparent cogent reasons exist now.

The above is standard functionality and feature in other GPS mapping applications. It inherently caters for the needs of all users in this regard, and offers complete flexibility and functionality.

The main purpose of amending unhide button functionality is to make available tap elsewhere on the map screen available for implementation of future functionality. In the interim, this also prevents buttons appearing when user only wanted coordinate information by tapping on the map. Coordinate functionality could eventually be reassigned to be access by another method, and additionally the actual position of the coordinate on the map screen marked for clarity. This is standard functionality and feature in other GPS mapping applications.

It can be stated any changes would not adversely affect any existing functionality or user.

Further information to be added.

low.flying.pigs