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 1
For those that may stumble upon this later I neglected to literally
"include" the xml in the main views xml
On Feb 10, 8:59 pm, Aaron Buckner wrote:
> 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 o
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 wrote:
> On Thu, Feb 10, 2011 at 7:45 PM, Aaron Buckner wrote:
> > The layout is contained in it
On Thu, Feb 10, 2011 at 7:45 PM, Aaron Buckner 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, this "dashb
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 firs
On Thu, Feb 10, 2011 at 7:35 PM, Aaron Buckner 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 time learning
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 wrote:
> On Wed, Feb 9, 2011 at 11:42 PM, Aaron Buckner wrote:
> > I don
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:
http://schemas.android.com/apk/res/
android"
On Wed, Feb 9, 2011 at 11:42 PM, Aaron Buckner 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 confused as to
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,
10 matches
Mail list logo
