Why are you trying to start a thread for the UI? This happens
automatically when your Activity is created so there is no need to try
and start another thread for the UI. You should only have to create a
background thread for your socket processing.
On Jan 14, 2:19 am, "[^MiSaTo^]" wrote:
> Hi ag
Hi Misato,
Like Dan said, you most likely do not want to create a separate thread
for the UI. Any UI updates should occur in the main thread (i.e. the
thread where the Views were created). Please check this How To for
handling expensive operations in the UI thread.
http://code.google.com/android
Thanks, I'll have a look at it.
I'm new at android developing and i think i'm a little bit lost.
On Jan 14, 8:17 pm, James Yum wrote:
> Hi Misato,
>
> Like Dan said, you most likely do not want to create a separate thread
> for the UI. Any UI updates should occur in the main thread (i.e. the
>
So, sorry to bother you again.
What i understand, is that i create the UI as the main Activity Class
and inside it i lauch the other thread.
In pseudo-code this will be like :
onCreate{
initialize the UI;
launch socket thread();
create Handler();
}
am i right?
On Jan 14, 8:17 pm, Jam
Misato,
I have included some code that I use and works great. I'm fairly new
to Android myself so there obviously could be other ways of doing it
as well.
Inside of my activity class I create the Handler object:
// Create a new handler object that will handle the messages
// sen
Thank you Dan.
I understand your post and appreciate your help.
I'll try it! :)
Sorry to bother, but i've never done concurrency.
On 15 ene, 17:51, Dan wrote:
> Misato,
>
> I have included some code that I use and works great. I'm fairly new
> to Android myself so there obviously could be oth
6 matches
Mail list logo
