[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Post 2297 has been updated for ease of reference to explicitly indicate this as a potential workaround in the interim.

Some further notes are below:

On some Windows CE based dedicated devices, the intended dedicated application settings are not application level but system level and thus would apply to GPS Cycle Computer. However, that is not necessarily desirable, and a user may wish to have different settings for each application. GPS Cycle Computer on Windows Mobile has facility to override system level settings and if implemented on Windows CE, would be able to have settings independent of the intended dedicated application, regardless of whether its settings were system level.

Furthermore: When application level, these settings are only applied when the dedicated intended application is running. When system level, some dedicated intended applications do not enable settings to be retained, but instead apply them when the application is running.

Ordinarily, the intended dedicated application was intended to run at all times the device was on, and either approach was sufficient for that purpose. However, that is not the case in this circumstance.

It would be undesirable for a number of reasons to have to run the intended dedicated application in addition to GPS Cycle Computer just to control these settings. For example, when running, even if GPS is not 'on', some dedicated applications prevent another application accessing the GPS port creating another complication. Again, ordinarily, that would not be an issue, there would not be any other applications. This issue is not insurmountable. However, device hardware specifications are. Some devices whilst having sufficient resources to run their intended dedicated application, or GPS Cycle Computer, may well be insufficient to run both at once in addition to GPS Port Splitting.

However, for devices with sufficient resources, where possible, both applications can run at once, with GPS Port Splitting if necessary, and means of switching between applications.

It was initially envisaged a standalone GPS Cycle Computer 'launcher' would be created. It would run when the device is first switched on and automatically make any system adjustments required, and install Microsoft .Net Compact Framework as required. It would then allow selection of the required application(s), i.e. GPS Cycle Computer, and / or intended device application, and perhaps others. It would incorporate GPS Port Splitting and Task Switching functionality.

As some devices lack usable hardware buttons, and for consistency, it was initially envisaged Task Switcher could be accessed by an unobtrusive discrete button, or similar, on screen and always on top but in a position dependent on the application in use. Task Switcher and Port Splitting functionality would only run if required when more than one application was started.

There are many considerations and various intended dedicated applications. Methods that would work with all and do not rely on functionality in any avoid creating unnecessary dependencies and potential future compatibility issues, would inherently be the most robust.

Similarly, whilst there are various existing separate third party 'launchers', GPS Port Splitters and Task Switchers, and scripting approaches utilising Mortscript, there are no existing integrated elegant solutions, that provide a single .exe file that runs on all Windows Mobile Platforms, let alone Windows CE5 and CE6 as mainly required, and without unnecessary dependencies.

Furthermore, if the GPS Cycle Computer project creates it's own 'launcher', there are no issues with licencing, compatibility, or third party software not being updated or becoming unsuitable for purposes as required. It may be possible to adapt and combine source code from some existing separate freeware open source projects. For each key aspect suitable projects with source code have been identified and are being considered.

It is clear at this stage as a minimum GPS Cycle Computer does require Volume, Back light Brightness and Back light Off functionality as described previously.

There may be other dedicated device functionality requirements, in addition to those and Exit Shut down, that become apparent as work progresses.

Further information to be provided when available.

Users that do not need, require, want, or will not use proposed functionality will not use it and are therefore not adversely affected, as existing functionality will not be adversely affected.

low.flying.pigs