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

The proof of concept differs from standard 4.12 beta 2 and upon first run starts without any message boxes, and also without any gap, working consistently in Windows CE 5 Emulated Environment. It does this as follows:

1. 'App maximised' is default on. It does not require selection by any means or usage of any .dat

(changed Form1.cs line 410 to bool AppMaximized = true; )

Unless 'App Maximised' is selected either by default, or by using a using a suitable GpsCycleComputer.dat if the context menu cannot currently be reached, GCC loads in landscape and not portrait orientation as required.

2. Message boxes that may otherwise display before the main GCC screen is reached as per screen grabs are either disabled or removed within the source code before compiling. Therefore these cannot now be displayed. These message boxes are normal, but their presence in conjunction with the current implementation of 'App Maximized' introduces an undesired effect.

Unless such message boxes are disabled, GCC loads in portrait orientation when 'App Maximised' has been selected by whatever means, however it can be seen there remains a gap between the GCC display area and the bottom buttons as the message boxes seem to interfere with this area scaling properly initially. It will rescale properly when Minimized using the Titlebar and then Maximised using Taskbar, if available not requiring any restart. Otherwise Exit and restart.

This confirms the causes of the issues being observed, as was the object of the proof of concept.

However, strictly, usage of the current implementation of 'App maximised' by default and resolving the issue with the initial message boxes when applicable is not the solution as it does not resolve incorrect orientation when not maximised or provide actual full screen when maximised.

It is important to understand App maximised is not the same as Full Screen in Windows CE. Full Screen is Full Screen. App maximised is App maximised, with Titlebar and Taskbar (if Taskbar ordinarily visible) remaining displayed. Windows CE requires a different technique to achieve Full Screen than Windows Mobile. Otherwise if using the Windows Mobile technique in Windows CE, it is only maximised and not full screen.

Further information and a coding example of how this may be achievable is here. It would obviously require some adaption to the GCC code and integration and does not require to be used in full, only the relavent parts. Having tested the example code I can confirm it does detect Windows CE and Windows Mobile functioning accordingly. It is possible the issues with orientation and message boxes may not occur in the first instance when the correct technique is used.

If necessary the Windows CE context menu technique previously detailed in post 2015 as quoted below could be integrated with the above to run only when Windows CE is detected present.

Details for the Windows CE 5 and 6 Emulator will be forwarded by private message.

Only the replacement .exe was required. Any existing .exe and .dat were to be deleted.

'Cant open GPS' as per screen grab 6, does not ordinarily occur on first run, it occurs after the main screen has displayed and then ordinarily requires a separate user interaction of pressing the bottom right button to switch on GPS, with the error only then ordinarily displayed when GPS is not configured or in usage by another application if not shared. It would be interesting to know whether the Medion S3857 has GPS on at all times when the device is on, or if GPS is off unless switched on in GCC (when configured), essentially whether this is device specific.

'Error! An unexpected error occurred in GpsCycleComputer.exe. DirectoryNotFoundException ....', It would be interesting to know if this also occurs in standard 4.12 beta 2. If not it is probably because I disabled / removed the source code for the message boxes, but did not disable / remove other source code that utilises that code, such as the directories selection code. Essentially I did only what was necessary for the proof of concept. In the emulated environment it only effected local\language selection, and with a somewhat different error, as per screen grab 7.

low.flying.pigs