I can't exactly figure out the reason of your problem, but there is a strange thing I observed too when developing my app. There are some situations (can't exactly describe the condition they appear), when a button on my form (as soon as I saw, the first in the order of buttons), is effectively not receiving events correctly, more precise when I tap on it, a wrong ctlEvent->controlID is generated (a big WORD value). That is a strange thing, and I solved the effect by always using a non-visible button in the form, which has the lowest possible ID. I don't know if somebody can reproduce this, but it is appearing on some forms, especially maybe when you have much forms in the resource.
Dan "Richard Coutts" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > Running gremlins, I get an "Unallocated Chunk" error every 200,000 events or > so that's proving to be a tough to track down, because when I put a break > point before the crash and step through the events, it doesn't crash. But, > if I let it run up to the crash, the Debug Stack window leads down into the > Palm OS's code, which I'm calling from FrmDispatchEvent. > > One odd thing, looking at the state of the variables, is that the event that > FrmDispatchEvent is passed is the ctlEnterEvent. But, when I look at the > data, the ctlEvent > controlID is a button that is not in the currently form > visible at the time of the crash. (But, I'm not sure if the form I'm seeing > on the screen was the active from when FrmDispatchEvent was called, though I > would assum it was.) > > Sorry for the vagueness of my post -- I'm hoping that someone has seen > symptoms like this before and can give me some insights as to whats going > on. > > I'm running POSE 3.5 with palmos35-color-en.rom and CW8.0. > > Thanks, > Rich > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
