Problem in the Notepadv3 tutorial code...

by Raymond Ingles » Wed, 12 May 2010 15:12:57 GMT


Sponsored Links
 I've been working through the Notepad tutorial (
 http://developer.android.com/guide/tutorials/notepad/index.html  ) and
it's been helpful. I'm aware that the second version has a bug, that
is fixed in the third stage. However, the third stage (Notepadv3)
still has a problem:

 Choose "Add Note", then change the orientation. The note editing
activity crashes when the orientation changes, in
ActivityThread.performPauseActivity() with a NullPointerException. I'm
not quite familiar enough with this platform to figure out what the
issue is. I thought it had something to do with saving the row, but I
thought I fixed that and it still bombs out.

 It's easy to reproduce the problem in the debugger. Can anyone
explain what causes the crash? This might be a very good thing to get
fixed; I presume a fair number of developers are going to look at that
code and assume it's "the way to do it"... Thanks for any help y'all
can provide!

--



Other Threads

1. Add a contact and get the LookUp key pertaining to it.

Hello everybody,

I want to add a contact(accepting the contact details from my the
application's activity) and after adding it, I would like to retrieve
the LookUp key pertaining to it.

I was able to add a contact using the following tutorial,
http://www.pocketmagic.net/?p=1819

But, In the above tutorial, the adding of contact it performed using
RawContactId and thus, I'll have access only to the RawContactId.

But, my application needs a LookUp key( not a RawContactId ) for
accessing the Contacts.

I found a solution(I am going to try it now) for this problem at,
http://www.pocketmagic.net/?p=1844
But, the solutions is little bit complicated(for a novice like me).

Please, provide some suggestions/code snippets which can help me out
in getting the LookupId for a contact that is added just now,
(provided, we have the RawContactId of the newly added contact).

Thanks for any help, in advance.

-- 

2. latest update ruins my orientation data

Hi all,

I'm developing a game and was using the orientation data to move the
player camera. All worked fined untill i updated my nexus s yesterday
and now my orientation data is giving strange results.

When I lay the phone on it's back and not move it,
the azimuth flips between -0.4 and 77
the pitch between -0.3 and 3
and the roll between -2 and 9.5

Values are estimates and there are no inbetween values, so it's either
-2 or 9.5
This causes the camera to flip between these values and is no good to
me.

Has anyone ever had this and know how can i fix this.
Many thanks for your help.

-- 

3. ViewGroup, how to intercept MotionEvent and then dispatch to target or eat it on demand?

4. QEMU-Bridging: Full host to Android-emulator communication

5. In-app billing 鈥?get price paid after successful purchase?

6. How to stop / terminate call?

7. Announce: tramp-adb.el (Access Android devices filesystem using Emacs TRAMP)