Menu items on device not appearing correctly

[Jim Burton]

On my simple DefaultForm application, the File menu defaults to having a single item, "Exit" -- the Exit item shows up fine on Intel, but on my WM 6.1 device it shows what looks like: [][] (A)

I created another meny item with the caption "hello" -- this also shows up fine on Intel but on the device it looks like [][](o)

BTW -- I'm impressed on how fast the app launches on the device :) It seems much quicker than with PPL 1.x

[kornalius]

Hi,

We are aware of this problem. We cannot reproduce it on the WM6.1.4 emulator, so it is pretty hard for us to fix it. Hopefully someone can help us.

[Jim Burton]

error log from the run...

PPL compiler v.2.01.0000

Filename : \my documents\untitled.ppc

Loading ppc file...
** warning ** Error linking function GETSYSTEMMENU from library coredll.dll
** warning ** Error linking function EXTFLOODFILL from library coredll.dll
** warning ** Error linking function FRAMERECT from library coredll.dll
** warning ** Error linking function GETTEXTEXTENTPOINT32 from library coredll.dll
** warning ** Error linking function SCROLLWINDOW from library coredll.dll
** warning ** Error linking function TRACKMOUSEEVENT from library coredll.dll
** warning ** Error linking function GETDEVICECONTEXT from library coredll.dll
** warning ** Error linking function SHOWSCROLLBAR from library coredll.dll
** warning ** Error linking function ENABLESCROLLBAR from library coredll.dll
** warning ** Error linking function MAPVIRTUALKEYEX from library coredll.dll
** warning ** Error linking function GETKEYNAMETEXT from library coredll.dll
(7,245 ms)
Completion time (7,753 ms)

** 0 error(s), 11 warning(s)

[argnob]

I have a similar problem with menus when an unaltered Desktop Form project is run on Windows Mobile.

The File menu, as displayed on the device, is preceded by an & and the Exit menu entry consists in two squares and the letter t.

Not that I'm optimistic that this detailed info will help you, Alain, but, so you have it, my device is an HP iPAQ HX2490b (Intel PXA270 processor) and my WM is Version 5.0 OS 5.1.1702 (Build 14366.1.0.1).

It's progress for me to finally get anything running on the mobile device. Took plenty of reinstalls. I guess the trick is, before reinstalling, to do a more substantial remove than is done by Add/Remove Programs or by running the uninstall PPL2 option from the Start Menu. I'm not convinced that my efforts to unblock port 1002 in the firewall helped, though this was sometimes what was complained of. The Firewall changes I made didn't solve the problem of not being able to run the program on the mobile device even after a reboot, whereas uninstalling PPL2 from PC and device and deleting the PPL2 folder on the PC (and a Norton Windoctor registry tidy up for good measure) did, in the end, result in the program running on the mobile.

At other times the button to run on the mobile device did nothing but I think the answer to that was that the Windows Mobile SDK hadn't yet had its registration key re-entered after that particular reinstall. At any rate, entering the key solved the problem. Perhaps in these circumstances, the program should prompt the user to enter their registration key rather than just ignore clicks on the run on mobile device icon.

I'm puzzled why CleverUpdate routinely re-downloads the software if asked to install it, even when the setup files for the most up-to-date versions are available locally.

[kornalius]

Hi, there are no mechanism in place in CleverUpdate yet to locate local setup files. I will look into this possibility.

Have you tried turning off your firewall completely just to try out? Is your device correctly connected via ActiveSync first?

[Jim Burton]

To get back to the menu issue :)

I've seen similar things when a control expected a plain-text but instead got Unicode, and vice-versa.

What can I do to help fix the issue?

[Jim Burton]

Bumpity-bump :)

what can I do to help you get the menu problem fixed?

[Jim Burton]

Heloooooo :(

[kornalius]

Sorry for the delay responding to this issue.

We will have a new version very soon 2.1.1 it willnot address this issue, however we will fix it for 2.12 interim before 2.2.