"Steve Orens" <[EMAIL PROTECTED]> wrote in message news:76419@palm-dev-forum... > > greetings, > > is DbgMessage() supposed to put up a dialog? it seems that if the program is > executing and rapidly calling DbgMessage() (one right after the other), i > sometimes get messages that are both logged to the Log Window and displayed > as a dialog. if i put in a for loop to delay the execution right after each > call to DbgMessage(), then the problem goes away, but naturally the > application slows down significantly. is DbgMessage() supposed to do this by > design? is there a faster, more correct way to write to the Log Window?
The debugger interface between the device/emulator and CodeWarrior isn't very robust with DbgMessages -- basically, the device sends out the message, but the protocol doesn't require a response from the debugger to acknowledge the message. You can read about this in the Debugger.html file included with POSE. Right now, it seems that the CW debugger isn't able to handle a high flow of these messages, but I'm not sure how POSE is deciding that the debugger channel is blocked and that it needs to pop up the dialog. In general, I agree with Keith and Adrian -- use the HostControl calls for logging, and only use DbgMessage for occasional messages. DbgMessage also has the nasty side effect of locking up USB-based devices like the Visor Prism if its get executed when the device isn't connected to a debugger. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
