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

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

Unfortunately I have been rather busy of late and unable to therefore post earlier.

Windows CE Context Menu:

In 4.12beta11, dependence on agyshell.dll has been successfully eliminated thus removing this unnecessary Windows CE device compatibility barrier for the benefit of all Windows CE device users. The current lack of animated user feedback that a press and hold action is in progress, given not all versions of aygshell.dll provided that, is unlikely to be an issue. New users are already automatically informed by the 'GCC - Important News' message box that context menus are available, and this could be made to appear on all Windows CE installations or upgrades when first used to ensure it is seen. It would be possible to implement a similar animation within GCC nonetheless if required.

Logging and Track2Follow:

In 4.12beta11, it can be observed when Multi-map is either 'off' or '1:1 zoom' (1:1 being default):

That on the map screen, that .gcc logs, .gpx tracks and .kml files, both created from .gcc files using File/Export within GCC, appear displaced by varying amounts dependent on the current zoom level of the map. In addition to .gpx and .kml files created by GCC, it can be observed at least some from other sources exhibit the same issue, but, at least those tested from gpsies.com, do not.

That whether displacement as above is apparent or not, map tiles, or parts thereof, that are present at the current zoom level, are not displayed at the bottom width of the map screen either immediately or at all, and instead a black or white area is shown dependent on whether White Background is selected from Menu > Options > Map Screen. When displacement is apparent, the vertical height of the section affected appears to correlate to the amount of displacement. When otherwise scrolling the map with smoothness and fluidity, this gives a flickering effect in that area.

Notably, it has not been observed to occur with, at least those tested, .gpx and .kml files from gpsies.com loaded as a track2follow.

Notably, when such .gpx and .kml files are in use, and map zoom levels present are are complete in the area being viewed without any missing tiles, the separate primary and secondary map effects previously documented are not observed.

In 4.12beta10, it can be observed when Multi-map is '1x zoom' (1x being default):

That the same files and maps as above do not exhibit displacement behaviour, or the effect on the bottom width of the map screen. This indicates these two specific issues have been introduced in 4.12beta11.

That .kml files from gpsies.com tested cause GCC to display a message box 'File only has Waypoints Use waypoints as track to navigate? Yes No' and no track is shown on the map. This specific issue is fixed in 4.12beta11.

In 4.12beta10, it can be observed when Multi-map is 'off':

That the same files and maps as above, lag / unresponsiveness becomes apparent. It can be observed from Task Manager that at least in some instances that whilst the lagging / unresponsiveness may give the appearance of a freeze or crash, GCC is in fact still running, but with abnormally high CPU usage. This specific issue is fixed in 4.12beta11.

That if the file is .kml, map is initially wrongly displayed at maximum zoom level 23-x (where -x is number of levels after the last zoom level of maps available, for example 23-8 where 15 is the last zoom level), worsening the lag / unresponsiveness. This specific issue is fixed in 4.12beta11.

Note: It has long been established the content of the users Map folder absolutely affects GCC on a device in a number of different ways, in turn creating a number of primary and secondary effects, and that this primarily stems from the 'infill missing tiles with nearest available lower zoom level tile' feature.

Further information to be added.

low.flying.pigs