On Jan 23, 2007, at 20:00 UTC, Chad Bullock wrote: > I'm not actually sure the correct way to deal with serial > connections... After sending a command and receiving a response, > should the port be immediately closed; or left open until my program > is done with it completely (probably when it's quit)?
Usually you'd leave it open until your program exits. I'm trying to think of why you'd ever want to NOT do that, but nothing comes to mind that doesn't seem really contrived. > Either way, when I close a serial control via serial1.close, the next > time I go to use it, it can't connect. This happens when using a > drag/drop serial control, and via instantiating by code. The only way > to get it to connect again is to unplug the serial/USB cable and > reconnect it (then it works one more time). Hmm. That's odd. What about if you quit and restart your app? > Just curious - When breaking in the debugger, how can I tell if the > serial connection is actually closed? I doubt you can. 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>
