When ABOUT Screen is viewed, the myAbout.ShowDialog() is called to display the ABOUT screen, which will/should automatically call the ACTIVATED Event which will display the below Message box. Below are the details of the change.Ī new ACTIVATED event has been added in the attched sample project for ABOUT (AboutForm.cs) screen. I have attached the Sample Project with this mail so that anyone can debug the issue. So I believe there should be something to look at perspective of Win CE7 OS or Motorola Device. I noticed the same behavior where the Activation event is not getting triggered upon calling Show/ShowDialog() in MC 9200 but is working fine in MC 9090.
In Order to verify if the issue is with the application or the device, I have added ACTIVATED Event call in CS_BarcodeSample1 project and tried executing it in both MC 9090 and MC 9200. But the same is getting executed as expected in MC 9090. Due to which the business logic inside the ACTIVATED function is not executed resulting this error. Technically Speaking, in MC 9200 when the NextGen Application's FORM.SHOW() action upon calling is not triggering the FORM.ACTIVATED event automatically. The issue is due to the Events in Application is not getting triggered properly. More info and the attached sample app we used to repro the issue. I tried updating to the latest version, and saw no difference in stability.Īre there any known issues to be taken into consideration for MC32N/CE7 devices for old project migrations? I checked for incorrect p-invoke calls, but all the calls used (hiding the start bar, setting the window to fullscreen) appear to release any resources they use, and I haven't found any obvious resource leaks. If I disable launching the MSP process in the background, the application will be much more stable, but not totally stable (still crashes, but takes significantly longer before crashing). Right now, the application launches the Motorola MSP client to check for updates after each order is sent. The crash is apparently happening somewhere in the main event loop of the MainMenu form. Stepping through the code, there is no obvious line of code or command that causes the crash. The MainMenu form is displayed from Application.Run(MainMenu), and it displays the Order form with a orderForm.ShowDialog() call in a using block. The crash occurs when the Order form closes and the MainMenu form is redisplayed. The crash occurs in the netcfagl.dll, and cannot be caught in the Visual Studio 2008 debugger. This crash does not occur on the MC3090s. On the MC32N0s the application crashes with an Access Violation to the desktop after sending 1-9 orders. Currently the application runs on MC3090s, and the client wants to upgrade to MC32N0 devices.
Global Solution Centers - Testing Services.
0 kommentar(er)
