Notepad does have certain limitations, as I see it. I worked with the tutorial extensively, and created a video series covering the material. Then, I was running quality checks on my release version of a program that monitors blood levels for diabetics, when something unsurfaced that had never was noticed in the Alpha versions. I have no idea if the appearance has anything to do with the fact that i upgraded to Android 1.1.
What I basically ran into, was that if you go to enter a level( or a Note in the Notepad example. ) and go from portrait to landscape, and then cancel it, you get a blank entry in your listview. Of note, the Notepad example doesn't have a cancel button, so my code is a bit of a tangent on that. I had hard coded the date time to dialogs, so they were always populated. What I did was write my own engine for the release version. I kept passing the bundles, so it would go from portrait to landscape and not lose data, nor when calling another app. However, I do not store to the database. I only store to the database upon pressing confirm, if you press cancel, the entry is canceled. That's what I found, I'm curious what others have found. John aka Radiolistener. On Mar 3, 3:30 am, "android.bu...@gmail.com" <android.bu...@gmail.com> wrote: > If the NoteEdit activity is killed, and the onSaveInstanceState() is > called, then the mRowId is saved into the Bundle. Thus the next time, > the user may be confused when he select another note to edit. Because > the NoteEdit activity will always check savedInstanceState firstly. > Is it a bug? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
