On Mon, Apr 23, 2012 at 10:45 PM, Jim Graham spooky1...@gmail.com wrote:
Why would setting the text of the TextView the second time cause a force
close (caused by a null pointer exception, where the string being
assigned was not null)?
Either:
-- The value t is null, or
-- The exception did
On Tue, Apr 24, 2012 at 07:02:52AM -0400, Mark Murphy wrote:
which is why we keep asking developers to post stack traces rather than
just exception names
Which would have been a lot easier to do, if I had it. Like I said, I'd
tried it earlier, and when it didn't work, just deleted it
24 апреля 2012 г. 16:33 пользователь Jim Graham spooky1...@gmail.comнаписал:
Which would have been a lot easier to do, if I had it. Like I said, I'd
tried it earlier, and when it didn't work,
If the exception happens while you're debugging, Eclipse will stop at some
seemingly random place
On Tue, Apr 24, 2012 at 06:32:13PM +0400, Kostya Vasilyev wrote:
If the exception happens while you're debugging, Eclipse will stop at some
seemingly random place (the corresponding catch block) and at that point,
there won't be a stack trace in the logcat yet.
I use the logcat directly from
Seems so simple...create a textview, prior to adding the arrayAdapter,
apply the header as myListVew.addHeader(t); then (or before) set the
text for the TextView (t) with t.setText(aString). (I believe the actual
variable's name was flashCurrentMode).
Here's basically what I did (I originally
5 matches
Mail list logo
