Form Closing Event Issue in WM6.5 device

[Y. Sivaram]

I have a strange problem in Windows Mobile 6.5 Acer Neo S200 device. In my
application in the Form closing event, I am showing a message box to get a
user input to decide whether to close the form or not. However in this
device while the message box code is getting executed (I.e. if I step
through the code the closing event and the message box code gets hit), but
it does not wait for the message box input and simply closes the form. The
message box briefly appears for a second and disappears. When I check the
same code in Windows Mobile 5,6 devices or 6.5 emulator it works fine. I do
not have any other Windows Mobile 6.5 device. Hence cannot verify this
behaviour.

Note my window does not have minimise button (it is a OK button) & the
closing event IS firing.

Any ideas?

Code I am using in the close event is

private void Form2_Closing(object sender, CancelEventArgs e)
{
DialogResult UserSelection = MessageBox.Show("Are you sure", "Test",
MessageBoxButtons.YesNoCancel, MessageBoxIcon.Exclamation,
MessageBoxDefaultButton.Button2);
if (UserSelection != DialogResult.Yes)
e.Cancel = true;
}


Apologies if it is considered as double posting. I have already posted this
to
http://social.msdn.microsoft.com/Fo.../thread/d17c042d-12e3-4b75-ba6a-409cc7c809a7/

But didn't get any solution.

 

[Peter Foot]

I've seen that MessageBoxes with only an Ok button are dismissed when you
tap anywhere on them which is a change to previous versions. But boxes with
2 or more buttons should exhibit the same behaviour as before. What you have
maybe a device specific bug. I can't duplicate this on a HTC Touch Diamond 2
running 6.5.

Peter

--
Peter Foot
Microsoft Device Application Development MVP
peterfoot.net | appamundi.com | inthehand.com
APPA Mundi Ltd - software solutions for a mobile world
In The Hand Ltd - .NET Components for Mobility

 

[Markus Humm]

I've seen that MessageBoxes with only an Ok button are dismissed when
you tap anywhere on them which is a change to previous versions. But
boxes with 2 or more buttons should exhibit the same behaviour as
before. What you have maybe a device specific bug. I can't duplicate
this on a HTC Touch Diamond 2 running 6.5.

Hello,

I don not like that change as far as I've seen yet this leads to the
impossibility to move that dialog around! So you can't read what's
behind it. One option would be to create a dialogue with OK and OKL
button, if the CF doesn't disallow this ;-) (or deletes the 2nd ok button)

Greetings

Markus

 

[Y. Sivaram]

Thanks Peter.

I too think it is a device issue. The device came with the ROM v1.002 and I
even tried upgrading to ROM v2.003. Still no luck.

I have raised this issue with Acer Support. I will keep you all posted.

 

[lidias13]

Any update from acer

Getting a similar issue

I have been using an Arcpad/Arcgis project for sometime now and have never had issues regardless of devices/OS the users are using.

However have just recently purchased a number of Acer Neotouch S200s (Windows Mobile Professional 6.5) and I am now getting error:

Permission Denied: 'Msgbox'

Everything I have been able to find on the web suggest server side issue largely related to ASP apps... but I am getting it on a local install of arcpad WHEREVER msgbox is used in coding, which includes my customized scripts but also Arcpad own script (for example when clicking on photo tab).

Anything that outputs any sort of msgbox or warning to the device screen (IE also happens when encountered a blank "required" field).

Have used HTCs in the past with 6.1 (possibly 6.5 too i would need to check) and had no issues. Have sent an email to Acer and am awaiting a response... but I have no idea why would be having issue with something so fundamental.
Is there an issue with vbs on NeoTouch or Smartphones in general?

 

[stratamodel]

Hi Iidias13,

I'm having the same problem with a new Magellan Pro10 running WinMobile 6.5. Any script that uses Msgbox generates this error:

www.stratamodel.com/images/Clipboard01.jpg[/IMG

Did you ever find out what is causing this problem for you? None of my ArcPad scripts will work on the new Pro10.