Problem - PPC2002 v WMforPPC2003

  • Thread starter Thread starter Paul Kay
  • Start date Start date
P

Paul Kay

Has anyone experienced anything like this, or have an insight either into
the cause or a workaround?

The Structure of my Application is :

Using VB.Net CF and the Windows CE Api for the Functions FindWindow and
SendMessage

AppA occupies a portion of the screen
AppB occupies a different portion of the screen
AppX has no form displayed but is running a background thread monitoring
StatusA and StatusB

If StatusA occurs, AppX uses FindWindow and SendMessage to close AppA
If StatusB occurs ditto for AppB

This works perfectly with PPC2002 even if the current active Application is
something else entirely... Contacts or whatever

But with WMforPPC2003
If for example StatusA occurs whilst AppA is not the current active
application (e.g. AppB is active or I have loaded a single application on
top) it appears to receive the message to close but leaves it's image in the
portion of the (Today) screen it occupied and it still appears in
Settings/Memory/Running Programs although the OS will allow a new instance
of it to be started.

And yet, same scenario but I have loaded several other applications on top
of my two apps e.g Contacts,Notes and Tasks or whatever then the SendMessage
isn't caught at all.

Testing done on an HP Jornada 568 for PPC2002 and an HP iPAQ 2210 for
WMforPPC2003

Is my problem to do with the SendMessage function, am I using the Windows CE
3.0 version, and how do I explicitly use the Windows CE 4.20 version on the
WMforPPC2003 device.

Any help/guidance would be much appreciated.

Regards
Paul
 
A simple DestroyWindow(hwnd) works for me in both versions of the OS, so I'm
happy for now. (inspiration found 2 thirds of a way down a bottle of Pinot
Grigio de Venezie, maybe I just shouldn't program sober)

Though I would still like to discover why SendMessage behaves differently in
each version of the OS
 
Back
Top