On Jan 26, 2007, at 1:42 PM, Chad Bullock wrote:
Makes sense
RB probably just reads an OS level buffer for the device which may
very well
still hold data you did not read last time before you quit
Ok, that's what I was thinking. Last question (I promise) - do you
have any
idea how to force clear/flush that other main buffer that's lying
around in
the system somewhere?
I've tried to just flush & close the port through RB, but the extra
data
still is stuck somewhere else lower down the chain. When I quit and
restart
the app, it is still there waiting. Thanks,
I suppose when you quit or start back up read everything you can
before you send your first command that the device should respond to.
If the device is constantly sending data then you'd need to find some
way to synchronize your reading with what it's sending (like "data
packet" markers , etc)
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
