This doesn't make any sense, though. If you're inside in.read(), you should be sleeping, waiting for the network transfer to complete. So the WebKit thread *should* have some time to process your loadUrl() requests .....
On Mon, Apr 6, 2009 at 1:21 PM, j <[email protected]> wrote: > > Mark, > > I have a nastier solution: > Put inside the while loop: > try { > Thread.sleep(100); > } catch (Exception e) {} > > It works. > > On Apr 6, 12:41 pm, Mark Murphy <[email protected]> wrote: > > j wrote: > > > Mark, your suggestion makes sense. I tried it. I created a separate > > > thread for downloading and uses a Handler to loadUrl instead of > > > calling loadUrl directly. > > > > > But the result is the same. The loadUrl executions get queued up. It > > > appears the downloading thread seems to have priority over the Handler/ > > > UI thread. > > > > Hmmmm...you could try calling setPriority() on the background Thread to > > try to ensure the UI thread gets more love. > > > > -- > > Mark Murphy (a Commons Guy)http://commonsware.com| > http://twitter.com/commonsguy > > > > Warescription: Three Android Books, Plus Updates, $35/Year > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
