[seekay]

hello there!

I have a problem where I'm sending some bytes to a dataOutputStream to a bluetooth serial port but not all bytes are being written before the stream is closed.

I'm making several writes of data and have tried flushing after every write and flushing again before closing but none of it helps.

I'm quite sure this is the problem anyway because if I leave the stream open (i.e. don't close it at all in the app) then all data gets written fine and I see the desired results on the bluetooth printer, however when I attempt to open a connection again I don't get anything...

Also, when I have the debugger attached to the bberry I get more bytes written to the port than otherwise (I presume as there's a larger overhead and everything runs more slowly so the connection gets closed slightly later than otherwise.

I've tried implementing a 'wait' (and catching the associated exception thrown), but I'm not 100% sure what I'm doing as I'm new to bberry development.

The wait part looks like :
//wait and close connection
long wait_time = 60000;
_dout.wait((long)wait_time);
System.out.println("Waiting to close connection...");
_dout.close();
_bluetoothConnection.close();
System.out.println("Connection closed...");

but it always generates an exception in this thread so I'm not really sure if I'm implementing it properly.

Any suggestions would be very much appreciated...

Regards,

[seekay]

Just in case anybody had the same problem (there were one or two on another forum), the solution was to implement a

try {
   sleep(milliseconds);
} catch(InterruptedException e) {
  //something here
}

Just after all my writing - works a treat! I find 5 seconds is enough - might try to fine tune it down...

Hope this helps someone...