[Touch Diamond, MDA Compact IV General] low.flying.pigs:
In response to feedback arising that can be addressed and or reproduced:

Visual appearance is a matter of personal taste. Rather than make any further hard coded changes, the colour of the line effect, and unavailable text if necessary, should be made user selectable as with other colour options (or somewhat less user friendly, set by text file as with other features, perhaps within the skin) catering for all allowing full flexibility. Nonetheless, 4.11 beta 13 is clearly discernible regardless of back light level or standard or black theme, and there arises no genuine confusion between unavailable and selected buttons. Facility to change text colour when button unavailable, and option to remove unavailable buttons and or text still have merit as they did when I originally proposed them.

As issues with Menu Screen Anomalies have now been raised, the below is provided that was scheduled for inclusion with other feedback still being compiled. This will now follow in due course.

Menu Screen Anomalies:

Taking the following forms: Stuck Pressed Button Only, Stuck Pressed Button and Line, Line Only

Variations of these long term known issues have been present since at least 4.10 beta1 (four point ten beta one) and are not resultant from any recent changes.

Stuck Pressed Button and Line:

Observed whenever a 'user prompt' occurs initiated from File/Export and / or Track2Follow buttons, when dismissed a line is seen coinciding with the bottom approximately of where the 'user prompt' was displayed, and the button image remains 'pressed'. It does not occur with Recall buttons and that prompt when there is no associated .dat file. The colour of the line depends on scheme selected: night = black, day = white.

Stuck Pressed Button Only:

Observed to effect File/Export and Track2Follow buttons. Image remains 'pressed' if option selected from context menu that leaves menu screen, and the menu screen is then returned to. Also observable where device manufacturer UI enhancement (such as HTC Sense) close feature for context menu is selected, instead of choosing an option on the list. If option from context menu is selected that causes a 'user prompt', the aforementioned stuck button and line effect is observed.

Line Only:

Observed wherever a 'user prompt' is on screen without a menu button press. In Windows Mobile 2003 SE, 5.0, 6.0 and 6.5 (and others possibly / probably) pressing the speaker icon on the taskbar displays the native volume control (some manufactures UI enhancements replace this). When dismissed by pressing again, approximately where the bottom of the volume control was is the line. Seemingly random command can be executed sometimes by carefully pressing or long pressing on line. Pressing on the line over the restore button displays the map. Other taskbar items such as signal might behave similarly. This has been present since 4.3 (four point three) when menu buttons were introduced.

Speed graph is not a selectable menu button when there is no speed data. It remains available from the Altitude graph in the context menu in this circumstance as that was not corrected when unavailable buttons were implemented. It is a known issue and will be corrected in due course.

Buttons are unavailable when the function is unavailable as above. This is a basic principle in computing. Enabling a graph button in such circumstances to then display 'no data to plot' on that graph screen, essentially reverting back to pre implementation, serves no useful purpose hence change in the first instance.

low.flying.pigs