The error was caused from the code setting up an instance of the objects in an area that is not active. I just went according to your code in your book. I gather that you looked at my code and determined that it was setup correctly.
Since I can't seem to get this to work properly, I have decided to go a different route by reading/writing a file to the default application directory. This way, I can create the values needed from the objects on the "setup" screen - radio buttons and text from the EditText object, and read them on the "main" screen. From there, I can then take those values and place them on the screen as well as use them for my calculation. Unfortunately, I don't know if there is a way to use "Global Variables" in a project which can be accessed any screen, anywhere in your project. Using global variables is not a good idea but it is a simple solution rather than saving/reading a file. Setting up a preferences screen is an interesting idea. I will have to try a test project to see how a person can create and read the preferences from one screen to another as well as make sure that the formatting of the other screen is correct. One simple test would be on your main screen have a textview ojbect that says "something goes here" as well as another textview object that says "radio button option goes here". Your second screen would have a and a couple of radio buttons that say option1, option2 as well as an edittext object where you could type something in. Once you return back to your main screen, see if you can read those preferences and place the values selected and typed in to the textview text. One textview would setText to what you typed on the other screen. The other textview would indicate which radio button you selected. Unfortunately, these radio button objects don't have values the same way html radio buttons work. With them, you can have an ID, Label, and a value. So one radio button could be like this: ID#1, "Option #1" (label), "30" (value). Perhaps in Java there is a way. Still learning, but for now this is the only way I can think of in order to set and pass values from one screen to another. Once I have figured out different ways using test projects, then I can implement them in my main project. I appreciate all your help and guidance in this area. Thanks again, :RB On Oct 1, 4:13 am, Mark Murphy <[email protected]> wrote: > On Fri, Oct 1, 2010 at 12:34 AM, rb <[email protected]> wrote: > > Thanks for the link to your book. I have tried your examples from it > > and now I get the app forcing to close. > > Use adb logcat, DDMS, or the DDMS perspective in Eclipse to examine > LogCat and look at the stack trace associated with your "force close". > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > Android Training...At Your Office:http://commonsware.com/training -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
