I just noticed an interesting thing that's happening with my serial stuff. I think someone either mentioned recently in this thread or earlier, that when my program quits, the serial port should be released (regardless of whether I close it or not - though just in case, I do close it to be sure)...
But when I've been trying to track down my bugs with this, the problem I mentioned before about the port/device not being used/recognized correctly after using it one time - another clue came up. When I do use it the first time, it works. Then I quit, then reopen my app and try again. If I just try to read the buffer in the dataReceived event of the device (without sending any more commands or anything), some of the old data from my last session pours in. So somehow it's been sitting in some (other?) buffer and I'm getting the tail-end of it upon the next connection; again this is after I've already quit my program and reopened it and reconnected to the serial. Does this sound right, or am I running into a possible bug in either RB, the USB driver for my device, or even a Mac bug? Thanks again everyone for the help. Chad _______________________________________________ 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>
