Search Results

. You can submit Runnables to this pool by calling: BA.submitRunnable public static Future<?> submitRunnable(Runnable runnable, Object container, int TaskId) You should pass null and 0 to... {false}); } } } }; ba.submitRunnable(r.... A RejectedExecutionException will be raised if more tasks are submitted. Raising events on the main thread In..., container, TaskId, event, throwErrorIfMissingSub, params); Runnable runnable...

Hello, I have been reading on how to create libraties for B4A and looking at some examples. I have two questions currently: - TaskID: I see this is used a lot. Is it just used as an identifier that is passed to eventhandlers so the B4A developper can determine where exactly it came from ? (because of being able to run the same method multiple times at the same time) ? - submitRunnable...
link: TaskId helps the user distinguish between different asynchronous tasks. - submitRunnable...

You should be using BA.submitRunnable not a Thread....
link: Maybe your Threading Lib can help me with that? im trying that right now......
link: stringCall should post the Runnable and return immediately so I don't see how it can block...
link: Thank you! it works! now i can handle it in the event... but i think that im still using the main ui...

is there any difference between this library, CallSubExtended library and Thread library ? CallSubExtended uses internally BA.submitRunnable, which seems to be the function to use with B4A to run something in the background....

I'm not familiar with the overlay library. I can say that you should avoid using additional threads in your code unless you don't have a choice. If you are reading the data from a database then you should use the async methods instead. CallSubExtended uses BA.SubmitRunnable to parallelize execution. It is very unlikely that the use of this library ends with an ANR. One of its goals is to avoid them. Without the code and without being able to reproduce the case, it's almost...

I've told you. You don't want to do this. BA.SubmitRunnable is better for one off asynchronous stuff....
link: necessary. Starting a Thread is an expensive operation whereas Ba.SubmitRunnable re-uses existing...

Any thoughts from the Java gurus on this? Being that it uses the object wrapper I'm not sure whether I should use BA.submitRunnable in the wrapper class or the normal java &quot;Runnable"...
link: You should learn a bit about Java multithreading. You can use BA.submitRunnable to submit...
link: , ConnectionDeniedException, TimeoutException{ ba.submitRunnable(new Runnable() { @Override...
link: .SubmitRunnable. I think normally the &quot;Runnable" option would be used in the original java class...

Once every time you submit it. this line : BA.submitRunnable(r, this,0); relaunchs the run() and howeve I send 10 messages to android I receive 1 message. I initalize again I can receive ONE new message thank you for you help...
link: ) { } } }; BA.submitRunnable(r, this,0...

Hi Erel, Can you give me an example of this? I cannot find much documentation on submitrunnable? And I do not understand how to use a runnable object....
link: B4A internal threads pool by calling BA.submitRunnable....
link: AsyncTask? Okay, now let me find submitrunnable. EDIT: Looks like runnable creates a new thread...

Read about the submitRunnable method. Thanks for the hint! A quick question ;-) if i initialize a pdfrenderer mPdfRenderer = new PdfRenderer(pfd); and store this is a class-variable.. Then i just use the renderer methods to get the pagecount, render only page x... Can i use the mPdfRenderer in a runable or do i need to create a new instance in the runable?...
link: complex PDF pages and then face the 'Force Close' dialog. Read about the submitRunnable...