Thanks. I've been using the old serial manager mostly, then converted to the new one for some USB stuff, but never played with the new funcs such as:
SrmSetWakeupHandler( ) SrmOpenBackground( ) So they might help. Part of my problem is that I need my program to operate sometimes in the absence of new serial data (say, at a near-fixed rate). It seems to me that the above will not help in such an instance. I could register for a notification for "sysNotifyEventDequeuedEvent", but that would be sporadic at best. Perhaps the notification handler could enqueue a nilEvent to keep the fire going, but I could see how that might be a burden on the rest of the system. GB "Chris DiPierro" <[EMAIL PROTECTED]> wrote in message news:89359@palm-dev-forum... > > This is not really true though for serial data as the question was referring > to. The serial manager gives you the ability to speify a callback that will > be called whenever n(you specify n) bytes are received on the serial port. > While not as good as a separate thread, this alleviates some of the problems > for that simple case. > > This wouldn't help you for a background data logger, but since he mentioned > the ability to spawn a thread, I assume he'd have the ability in his app to > use this as well, and best of all, it's been available for a long time now > :) > > > > > Are there any other pointers or options for those of use who > > > want to collect and/or massage serial data in the background? > > > > no.. all you have is the notification manager. register for > > events, and, it will send them to you. no hacks, TSR's, multi > > threading.. nada.. :) > > > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
