hi there

Hello

I have a question regarding Android Preferences.

I'm hoping you can help me answer.

I am writing an App that is using Preferences. I have the preference screen set up. On the onResume() function, I set my preferences based upon what the user selects on the preference screen.

However, when the user first enters the Preferences screen, the defaults preferences (as defined in the xml) always appear.

Do I need to add some code to get the preference screen to display the current application settings/preferences?

Okay. I'll do that. But just to clarify. In the onResume() function of the main activity, I am reading the preferences and using those to set various states in my App. But upon startup, could there be a mismatch of what the preference screen is displaying and what is actually set in my App?

I am indeed using getDefaultSharedPreferences(). I will look over the preference example more closely to see why I am getting a mismatch. Would there normally be any code in the instantiation of the Preference class?

other than the call to addPreferenceFromResource(...)

I'm sorry, I mean in the definition of the PreferenceActivity class.

Great! Thank You, appreciate the help! By the way I really enjoy your books. I am just getting started in Android Development, and your books have been an invaluable resource. I almost bought the print version, then found out about Commonsware.

I have a question regarding AudioRecord..

i have one. and also i think commonsware is great. i just subcribed last week.

there are two http stacks(java.net and the apache one) in android is there anyone more suitable then the other?

are there benefits/or is it good practice to use a contentprovider within my app, even if i don't plan to make the provider available to an outside application?

Quick Question: If I am iterating through a for loop, is it okay to use Array.length as the condition of the for loop, or is it recommended in Android to copy the length to a local variable and use that as the condition? (ie. for (int i=0;i<myArray.length;i++)

thanks

thanks!

i am building in eclipse right now and the project i have doesn't have a build.xml. i would like to build from the command line. can i generate the build.xml file ? ( sorry if that was covered in your books, i am not very far in yet)

great excellent, i will try that out

I am a bit confused as to what method of Threading to use? I currently create a background thread and communicate with the UI thread via Messages and Handlers. I noticed you mentioned that the Asynctask is easier to use as Android handles much of the maintenance. Is that the only difference between the two methods? Is one method better suited to long running background tasks than the other?

long running as in minutes to hours. But only running when the Activity is on screen and viewable.. (ie. not a service).

Is there something inherent to AsyncTask that makes it more suitable for tasks that last only a few seconds?

I see. Thank you for the clarification!

One more question. When Android puts my Activity to sleep, am I correct to assume all my instantiated objects will still be in memory when it wakes up my Activity? Can I still assume that if my task is killed and then re-started by the system?

by sleep, I mean perhaps the user pressed the back button and onPause() is called.

i see. I'm still trying to wrap my head around the activity lifecycle. So if onPause() is called, all my instantiated objects are still in memory, but if onStop() my instantiated objects are destroyed?

hi, Mark.

I see.

So, it is safe to assume my instantiated objects are still in memory until onDestroy()?

when does onSaveInstanceState() get called?

Thank you very much for your answer!

no, just wanted to check things out

is 1.5 what most people target nowadays as minimum supported version?

i see, thanks

Mark, thank you for answering our questions. I look forward to your next office hours!

well, thanks again... all the questions and answer were very informative

bye