Hi All! I have this weird problem, probably due to my lack of understanding, but anyway I am hoping that some kind soul out there will enlighten me. I have an application which should be able to run under OS 2.x 3.x. I am using the 3.5 SDK and sofar it has worked allright. But just today I decided to compile using the O2 optimization and not the debug option which I allways use in the beginning of an project. Now this is the behaviour that I see: Under OS 2.x everything is fine. Under OS 3.5 everything is fine Under OS 3.1 & 3.3 I somehow get the event enqueing disabled on some forms. Suddenly no buttons or any other UI elements on that form functions. In the below log the form in question is ID 1031. the button I try to use has ID 1035. This is what I see in the POSE log when running the -O2 compiled prc: 3.088: <- EvtGetEvent: menuEvent ItemID: 1010 3.088: -> EvtAddEventToQueue: frmCloseEvent ID: 1003 3.088: -> EvtAddEventToQueue: frmLoadEvent ID: 1031 3.088: -> EvtAddEventToQueue: frmOpenEvent ID: 1031 3.088: <- EvtGetEvent: frmCloseEvent ID: 1003 3.128: <- EvtGetEvent: winExitEvent Enter: 00000000 Exit: 00001D80 3.128: <- EvtGetEvent: frmLoadEvent ID: 1031 3.133: <- EvtGetEvent: winEnterEvent Enter: 00001D80 Exit: 00001D80 3.133: <- EvtGetEvent: frmOpenEvent ID: 1031 3.213: <- EvtGetSysEvent: penUpEvent X:29 Y:41 3.213: <- EvtGetEvent: penUpEvent X:29 Y:41 4.132: -> EvtEnqueuePenPoint: pen->x=241, pen->y=112. 4.132: <- EvtGetSysEvent: penDownEvent X:15 Y:144 4.270: -> EvtEnqueuePenPoint: pen->x=-1, pen->y=-1. 4.270: <- EvtGetSysEvent: penUpEvent X:15 Y:144 4.270: <- EvtGetEvent: penUpEvent X:15 Y:144 4.461: -> EvtEnqueuePenPoint: pen->x=241, pen->y=112. 4.461: <- EvtGetSysEvent: penDownEvent X:15 Y:144 4.461: <- EvtGetEvent: penDownEvent X:15 Y:144 4.608: -> EvtEnqueuePenPoint: pen->x=-1, pen->y=-1. 4.608: <- EvtGetSysEvent: penUpEvent X:15 Y:144 4.608: <- EvtGetEvent: penUpEvent X:15 Y:144 4.815: -> EvtEnqueuePenPoint: pen->x=241, pen->y=112. 4.815: <- EvtGetSysEvent: penDownEvent X:15 Y:144 4.815: <- EvtGetEvent: penDownEvent X:15 Y:144 4.967: -> EvtEnqueuePenPoint: pen->x=-1, pen->y=-1. As you can see all I get after the frmOpenEvent on ID:1031 is pen events. Now this is what i get if I run the same piece of code that has been compiled with the -DDEBUG: 11.343: <- EvtGetEvent: menuEvent ItemID: 1010 11.343: -> EvtAddEventToQueue: frmCloseEvent ID: 1003 11.343: -> EvtAddEventToQueue: frmLoadEvent ID: 1031 11.343: -> EvtAddEventToQueue: frmOpenEvent ID: 1031 11.343: <- EvtGetEvent: frmCloseEvent ID: 1003 11.373: <- EvtGetEvent: winExitEvent Enter: 00000000 Exit: 00001D80 11.373: <- EvtGetEvent: frmLoadEvent ID: 1031 11.373: <- EvtGetEvent: winEnterEvent Enter: 00001D80 Exit: 00001D80 11.373: <- EvtGetEvent: frmOpenEvent ID: 1031 11.468: <- EvtGetSysEvent: penUpEvent X:37 Y:40 11.468: <- EvtGetEvent: penUpEvent X:37 Y:40 12.329: -> EvtEnqueuePenPoint: pen->x=240, pen->y=111. 12.329: <- EvtGetSysEvent: penDownEvent X:16 Y:145 12.329: <- EvtGetEvent: penDownEvent X:16 Y:145 12.329: -> EvtAddEventToQueue: ctlEnterEvent ID: 1035 12.329: <- EvtGetEvent: ctlEnterEvent ID: 1035 Here it works, but why doesn't it work under 3.1 & 3.3 ???? Why can I get it to work with the DEBUG option, but not with a regular O2 compilation ?? Has anyone any ideas as to where the problem may be ? TIA Kim. -- Kim M�lgaard [EMAIL PROTECTED] http://come.to/moelgaard -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palm.com/devzone/mailinglists.html
