r_z_aret
Sat May 12 15:00:56 CDT 2007
On 11 May 2007 12:14:31 -0700, Mike <mlandis001@comcast.net> wrote:
>Can anyone think of a reason how an application that runs fine on an
>emulator could receive (what appears to be) an infinite number of
>WM_PAINT events when running on an actual device?
My best guess is that something in your WM_PAINT handler is triggering
a repaint. Showing us that code might help.
Until you know otherwise, I recommend assuming the bug is in your
code, and the fact it shows only on real devices (or the other way
around) is an artifact. Many of my bugs that showed on one platform
but not another were bugs in my code that should have showed on all
platforms. Only a few were caused by bugs in one of the platforms.
Some were caused by differences that I hadn't counted on (some
platforms are more prone to refreshing screens).
>
>At the moment, I'm debugging in EVT3 targeting a PPC'02 device (Dell
>Axim x5), but I suspect the same behavior on WM5 emulator vs. device.
The emulators that came with the SDKs for eVT 3 and eVT 4 are
notoriously unreliable as predictors for how well code would run on
real devices. The emulator that comes with VS 2005 seems to be a much
closer approximation to real hardware.
>It's an MFC application written in C++. All dialogs are rock solid
>except one that includes an OnPaint handler to draw a plot region.
>
>Any suggestions for things I could investigate?
Have you tried stepping through the code in your WM_PAINT handler to
see whether something triggers a WM_PAINT message?
>
>Thanks, Mike
>
http://pnmx.com/
-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).
Robert E. Zaret, eMVP
PenFact, Inc.
20 Park Plaza, Suite 478
Boston, MA 02116
www.penfact.com