On Wed, Oct 15, 2014 at 12:03:28AM -0700, Will Christiansen wrote: > So what I think you need to do it follow Nobu Games suggestion about the > premature closure.
Of course I should...that's how I had it originally. But as I've said, when I do that, Eclipse whines about it not being closed. Here's how it looks now (same as several time in the past, while trying to figure out where the problem is: --------------------------- CUT HERE --------------------------- <?xml version="1.0" encoding="utf-8"?> <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"; android:layout_width="fill_parent" android:layout_height="wrap_content" android:background="#000000" android:orientation="vertical" tools:context="com.jdgapps.andgtbrew2.AndGTbrew2" > <ScrollView android:layout_width="fill_parent" android:layout_height="wrap_content" > <LinearLayout android:layout_width="match_parent" android:layout_height="fill_parent" android:gravity="center_vertical|center_horizontal" android:orientation="vertical" > buttons, etc..... --------------------------- CUT HERE --------------------------- > It can't find the layout_width attribute because you are closing that XML > tag before it's set. Since you've tried that and the XML looks valid > (besides the premature closure) you should try to fix the XML like Nobu > Games suggested and then clean your project. I haven't used Eclipse in > quite some time but I believe it's under *Project *-> *Clean*. Trust me, I know that, and that's not why it was origninally complaining about not finding the layout_width---it was force closing because it wasn't finding it in the ScrollView params---the exact same ones shown above, btw. And if I don't close it the way we all know is wrong, Eclipse whines about it not being closed at line 2. As I mentioned in another response, I even tried joining all the lines together so it was ALL line 2 (up to the '>' in the spot where it's supposed to be)....no change...Eclipse still whines and refuses to build it. > If Eclipse still continues to whine, try removing the > tools:context="com.jdgapps.andgtbrew2.AndGTbrew2" line of code. In this > instance Eclipse is wrong in saying you should close it on line 2 instead > of line 7. I tried removing that---no change. And yes, Eclipse is definitely wrong, you know that, I know that, we all know that...but sadly, Eclipse doesn't know that, and it refuses to recognize that it's wrong. Until now. Strange...very strange. I just did a few undos, got back to what failed a few minutes ago, and THIS TIME, Eclipse not only built it, it didn't force close, AND I got what I was expecting on the display. I'd go back to the older version, but I'm also working with games and AndEngine, and it doesn't like the older versions of Eclipse (you know, the ones before it started crapping out all the time). This is not the first time I've seen Eclipse fail, fail, fail, fail, fail, fail, fail, and then build without errors, all on the same bit of code (sometimes from known-working examples or my own previously-working code). I just wish I knew how to skip the repeated failures to build and go straight to Eclipse working right the first time (like it used to). Thanks, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4) | "Now what *you* need is a proper pint of [email protected] | porter poured in a proper pewter porter < Running Mac OS X Lion > | pot.." ICBM / Hurricane: | --Peter Dalgaard in alt.sysadmin.recovery 30.44406N 86.59909W | -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
