M
Matt Gilarde
Guest
You may be able to figure out what's causing the frame to be realized by setting a watchpoint in the debugger on the HWND of a widget in the frame. I tested this with a simple program. DEFINE VARIABLE a AS CHARACTER NO-UNDO. DEFINE VARIABLE b AS CHARACTER NO-UNDO. DEF FRAME f a b. ENABLE a b WITH FRAME f. BELL. BELL. WAIT-FOR GO OF FRAME f. I started the program in the debugger and set a watchpoint on a:HWND. Then I continued execution. The debugger stopped on the first BELL statement, indicating that the ENABLE statement caused a to be realized. You can't test the frame's HWND this way because there appears to be a bug in watchpoints which doesn't allow an expression like "FRAME f:HWND".
Continue reading...
Continue reading...