[android-developers] Re: Adding a new View causing Force Close

2011-02-12 Thread Indicator Veritatis
Indeed: there is even a pretty good tutorial specifically on using the Eclipse debugger at http://www.ibm.com/developerworks/library/os-ecbug/. A source on more generic Eclipse topics is: http://www.linuxtopia.org/online_books/eclipse_documentation/eclipse_workbench_user_guide/index.html On Feb

[android-developers] Re: Adding a new View causing Force Close

2011-02-10 Thread Aaron Buckner
Thanks for taking the time to look at this and help me. 1. I'm not sure what you mean/how to step through the debugger 2. I figured you meant that my view was not defined 3. Here is the XML layout: I've tried something as simple as this: ?xml version=1.0 encoding=utf-8? LinearLayout

[android-developers] Re: Adding a new View causing Force Close

2011-02-10 Thread Aaron Buckner
Also when I check my R.java.id section under gen it shows the owners_screen id I'm not sure if that helps... it links to public static final int owners_screen=0x7f070016; in the R.java file On Feb 10, 12:50 am, TreKing treking...@gmail.com wrote: On Wed, Feb 9, 2011 at 11:42 PM, Aaron Buckner

Re: [android-developers] Re: Adding a new View causing Force Close

2011-02-10 Thread TreKing
On Thu, Feb 10, 2011 at 7:35 PM, Aaron Buckner nagm...@gmail.com wrote: Thanks for taking the time to look at this and help me. 1. I'm not sure what you mean/how to step through the debugger I'm assuming you're using Eclipse. If you don't know what this means, you really need to spend some

[android-developers] Re: Adding a new View causing Force Close

2011-02-10 Thread Aaron Buckner
Ok I'l spend some more time looking into the debugger tonight (yes using Eclipse) The layout is contained in its own xml file labeled owners.xml I tend to seperate each view into separate xml files to keep it easier to manage. here is the other code requested : /** Called when the activity is

Re: [android-developers] Re: Adding a new View causing Force Close

2011-02-10 Thread TreKing
On Thu, Feb 10, 2011 at 7:45 PM, Aaron Buckner nagm...@gmail.com wrote: The layout is contained in its own xml file labeled owners.xml I tend to seperate each view into separate xml files to keep it easier to manage. That's good practice. setContentView(R.layout.dashboard); Here,

[android-developers] Re: Adding a new View causing Force Close

2011-02-10 Thread Aaron Buckner
Nope!!! I knew I was missing something simple THANK YOU for your time! Thats what I get for taking a couple days off and getting out of town... you forget the simple stuff On Feb 10, 8:49 pm, TreKing treking...@gmail.com wrote: On Thu, Feb 10, 2011 at 7:45 PM, Aaron Buckner nagm...@gmail.com

[android-developers] Re: Adding a new View causing Force Close

2011-02-10 Thread Aaron Buckner
For those that may stumble upon this later I neglected to literally include the xml in the main views xml include layout=@layout/owners android:id=@+id/owners_screen android:layout_above=@id/navigation / On Feb 10, 8:59 pm, Aaron Buckner nagm...@gmail.com

[android-developers] Re: Adding a new View causing Force Close

2011-02-09 Thread Aaron Buckner
If I comment out the OwnerScreen.setVisibility statement and leave the findViewById statement there is no force close (of course there is no call to the OwnerScreen object at that point, I don't understand how it could be null though, I basically copied the statements for MyRideScreen and the XML,

Re: [android-developers] Re: Adding a new View causing Force Close

2011-02-09 Thread TreKing
On Wed, Feb 9, 2011 at 11:42 PM, Aaron Buckner nagm...@gmail.com wrote: I don't understand how it could be null though Step 1 - step through your debugger to confirm this. I basically copied the statements for MyRideScreen and the XML, Copying and pasting leads to many errors. so I'm