On Jan 23, 2007, at 21:48 UTC, Chad Bullock wrote: > All I have in the test serial.datareceived event is: string1=string1 > + me.readall > > Like you said, when the exception is raised, the popup just lists > tons of DataReceived fires, but even the first one doesn't contain > any useful info that I can see, and it won't track back to anything > before that.
Hmm. That's really strange. I've never seen anything like it. If that's all that's in DataAvailable, I see no way it should be possible for another DataAvailable to fire before the first one completes. > I was guessing that whatever the other serial port it's > connecting to (not the one I want), is sending a ton of unwanted data > and it's just overloading it. No, at worst that should cause data to drop out of the buffer. Shouldn't affect your code in this way. > > I don't know. You should never count on the indexes; much better > to go > > by the port name. > > When offering the user a list of all serial ports using the > serialportcount, and they pick one, I wasn't sure how you'd assign > the serial control's port using anything other than its index... Well yes, you use the index for that. I just meant, don't count on it being the same between runs of your app. Best, - Joe -- Joe Strout -- [EMAIL PROTECTED] Verified Express, LLC "Making the Internet a Better Place" http://www.verex.com/ _______________________________________________ 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>
