Thread String

by Bobbie » Fri, 06 Mar 2009 14:01:09 GMT


Sponsored Links
 I am trying to pass a string variable to a thread, but as soon as the
app gets to the thread that is requesting the variable, the
application crashes.  Any ideas?  Can you show me some examples of how
to pass a public string to a thread?  Please let me know.  Thanks!
--~--~---------~--~----~------------~-------~--~----~



Thread String

by Bobbie » Fri, 06 Mar 2009 20:56:49 GMT


 It's a really strange situation.  I can pass other strings to a
thread, but this string for some reason won't be passed.  The string
is:

static String sesid = "";

I have other static strings declared as well and they are working
perfectly fine.

Bobbie






--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Thread String

by Stoyan Damov » Fri, 06 Mar 2009 21:03:12 GMT


 What do you mean by "pass a string to a thread" - this doesn't make any sense.
Then, when your app crashes, what does the stack trace look like?





--~--~---------~--~----~------------~-------~--~----~



Thread String

by Bobbie » Fri, 06 Mar 2009 22:55:27 GMT


 Nevermind, I'm an idiot.  The thread was trying to call something that
didn't exist and I didn't see the line of code in there.  Sorry about
that!







--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. how to disable a button

Hi

does anyone know how to disable a button ?
thank you

luka
--~--~---------~--~----~------------~-------~--~----~

2. Call out to the community about the poor quality of Android's error messaging

you will probably not like what I'm going to say, but: ranting on the forum
is going to have very little results here.

even if there are Android developers who read them (and a fewer that even
answer certain questions) they are all very busy at the moment. what this
means is that the best way to report that kind of problem (i.e. "weak error
reporting") is to *use the public issue tracker*.

   - register an issue, and chances that the problem will be seen and
   reviewed by a relevant member of the development team is increased


   - describe your problem as precisely as possible, trying to nail it to
   the simplest possible code snippet or instructions. this also dramatically
   increases the chances of seeing the issue fixed / answered dramatically in
   the next SDK release

of course, I'm talking about problems that you want to communicate to
Android engineers. feel free to use the forum to ask other members to see if
there aren't simple work-arounds / way of using the system or if they have a
solution for it first.

sadly, your original post didn't contain any meaningful information we can
use to track exactly the error reporting weaknesses you're talking about
(and I certainly don't deny they exist).






--~--~---------~--~----~------------~-------~--~----~

3. How to use ANSWER_ACTION

4. GTalk Service IM Documentation + Sample Apps

5. GTalk Data Message

6. Android Programming Guide

7. Mail API