posted 05-30-2007 06:01 PM         

---

I'm converting a stand alone program to run as part of an MDI app in a MDI Child window. The original program used EZ_ConvertMousePos to determine the mouse position over a canvas control, and all worked well. However, when the canvas control is in the MDI Child window, EZ_ConvertMousePos causes the entire application to abruptly terminate. No error or GPF is produced--and even Windows XP fails to display it's famous "We had to close this program..." message box. If EZ_ConvertMousePos is eliminated, everything works fine. (It is necessary to use another technique to determine the mouse cursor position.)

Is there something in EZ_ConvertMousePos that prohibits it from working on an MDI Child form? I also tried using EZ_ActiveMDIChild to obtain the form name, thinking this might be necessary, but it made no difference. The program still terminated without notice.

posted 05-30-2007 08:04 PM         

---

Something else may be amiss.

Use a debug window and see what events are being generated. If your program accidently generates an infinite loop you can crash it.

EZ_ConvertMousePos shouldn't have any problems, unless you pass bad window handles. This command calls ScreenToClient and ClientToScreen api functions to convert mouse coordinates.