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

Many thanks for 4.11 beta 14 and source code. Appreciated as always.

The bug detailed are mostly fixed as below. Unable to test keep GPS on, with which no issue was experienced in the first instance so unable to confirm any effect.

Regarding keep backlight on, when GPS is on, screen now stays on regardless of Windows Settings overriding as intended. Disabling this override via Menu > Options > GPS > 'Safe Energy: do not keep Backlight on' works also, but currently requires that GPS must be switched off and back on again, before it takes effect. There is perhaps scope to eliminate that requirement. Post 1890 updated accordingly for future readers.

Menu page looks now as originally envisaged with addition of grey text for unavailable buttons.

Regarding menu screen anomalies, stuck pressed button only can still be observed where device manufacturer UI enhancement (such as HTC Sense) close feature for context menu is selected as previously detailed. The Line Only effect remains also as previously detailed.

Regarding pressed images, apart from the three bottom buttons which function as intended and also give feedback for press and hold functions, on the menu page, pressed images are now only seen when a button is pressed and held if that button has no context menu, and currently there are no press and hold functions thereon. Perhaps pressed images should be retained at least for the time being, at least for the bottom three buttons.

There is however potential scope for optimisation. Removing all the buttons as embedded resources from within the .exe, which seems a throwback to before skin was implemented, would reduce significantly the size of the .exe and at least in some respects make GCC more efficient. Currently the embedded resources are redundant if a skin is in usage. This change lends itself towards optional skin dependent on day or night theme, and skin selection in general. Installed correctly there would not arise a circumstance where GCC ran without a skin folder with buttons therein, GCC could warn in this instance, and or display text in place of the button. This would need only be for the lower three buttons, the menu page already having text.

The issue has been exhaustively previously detailed.

It has never been definitively confirmed anyone can still actually successfully upload a .gpx converted from a .gcc from within GCC consistently without fail. It would enormously useful if that could be established.

Either way it is not entirely conclusive as to where the issue lies. If it works as at 4.11 beta 14 for some, and not others the issue remains essentially unresolved.

Having conducted Network Protocol Analysis and essentially exhausted again for now testing possible, all that remained was source code examination. Comparison of the relevant parts to the crossingways example of what is required seems to me there may be discrepancies with clientInformation=string: as was brought to your attention.

Your understanding and familiarity with the GCC source code far exceeds my own at this early stage. Has there been a change to what crossingways requires?

low.flying.pigs