Search Results

New video tutorial: 256762156 AsyncStreams allows you to read data from an InputStream and write data to an OutputStream without blocking your program. The reading and writing are done with two separate threads. When new data is available the NewData event is raised with the data. When you write
link: Michael, there is really nothing special about AsyncStreams. You just need to initialize it in non-prefix mode. I recommend you to start a new threa
link: I would like to use AsyncStream. 1) May i know how can i TEST this code from post #1? install on 2 device? 2) How can i establish CONNECTION? Please h
link: Is there any kind of "DoEvents" for AsyncStreams? Using USBSerial, we have noticed it is necessary to finish one subroutine in the main activity befo

It is part of RandomAccessFile library. Make sure NOT to use prefix mode with your VB.Net app. Tip: start with this example: Network + AsyncStreams + B4XSerializator
link: Hello Everyone I'm sorry for question, i would like to build Android client application that it make comunications and share messages with VB.net sof
link: Thank You a lot @Erel

No. All the communication happens in the background. You can call AStream.SendAllAndClose to make it close automatically after it is done sending.
link: AsyncStreams is an asynchronous method and does not block the main thread. But is it possible to know when it finishes transmitting data with aSyncStr
link: I use a data end signature at the end of the byte stream and when this is received I execute the code that has to follow. Also when you send data (on

Please use code here... tags when posting code. AsyncStreams (in non-prefix mode) returns the data exactly as it returned from the native code. I'm not sure that I understand your code. Use the debugger and check the values of buffer before you do anything else with the data.

The AsyncStreams reading and writing are done with two separate threads. it works in the background. I think the problem is how you handle the incoming data rather than manage it to background.
link: Yes but when debugging. For example when my programm is in a loop doine something, and then data is coming then it goes to asyncstreamsnewdata and com

It doesn't matter. Your code always runs on the main thread. Make sure that nothing in your code runs slow and everything will work. AsyncStreams takes care of managing the network communication using background threads.

If you are only writing then there is no difference. AsyncStreams takes care of checking whether there is new data and raises the NewData event when the data is available. AsyncStreams also raises the Disconnected event if the connection breaks. However it will never happen with serial ports.
link: My mistake. I'm too used to working with AsyncStreams. If you are only writing to the stream then use: Serial1.Stream.WriteBytes(ArrayAs Byte(0x99, 0
link: It's worked! Yes, I asking for this example because I found many of the example in this forum using "AsyncStreams" and I'm not quite understand wha

J'ai peu d'expérience dans ce domaine, mais je me suis amusé avec Arduino pour écrire la documentation pour B4R. Dans B4A, pour AsynchStreams il y a deux méthodes d'initialisation: AsynchStreams.Initialize (In As InputStream, Out As OutputStream, EventName As String) AsynchStreams.InitializePrefix (
link: Dans la perspective(plutôt négative pour le moment !) d'échanger des données(autant envoyer que recevoir) par BLUTOOTHE entre un ARDUINO et B4A, J'ess

The question is not really about AsyncStreams. AsyncStreams sits above a communication channel and manages the transfers. Your socket related code should support IPv6. It is supported by default.
link: Hi, I made an app that sends some small chunks of (GPS) data to a server using AsyncStreams (currently unencrypted) and to the IPv4 address of the se

AsyncStreams has nothing to do with encoding. AsyncStreams sends and receives bytes.
link: Update: Summarizing, the problems that generated the error on AsyncStreams were three. None of these three errors were detected by the ReleaseLogger,
link: This observation was very helpful to me. The aSyncStream instance was released due to premature closure of the stream
link: I guess that the class instance where AsyncStreams is still running was released before the event was raised. Add a reference to the class so it won't

Powered by ColBERT