MBellish Text Picker
0
Difficulty: Medium
In this activity you will add the Text Picker function to the MBellish application.  The Text Picker will allow you to annotate your picture, and allows a choice of font and text color.
MBellish Text Picker

It crashed! I don't know why!

sort by: newest oldest
August 12, 2009 at 02:31 am - by estelendur (3 Posts)
icon
I typed everything in exactly as it is in the instructions, but when I tried to run it in the emulator, MBellish crashed.
August 13, 2009 at 01:19 pm - by RockyMtnBrain (2 Posts)
icon
Cool.  I see you got a few more of the activities completed, good job!  Coming down to the wire, I'd encourage you to take on the challenge activity.  Good prizes to be had, G1 Android phones from T-Mobile and/or some cash!
August 13, 2009 at 10:33 am - by estelendur (3 Posts)
icon
I went through the instructions again and figured out that I had omitted a line of xml: the category tag for the activity in the manifest file.
August 12, 2009 at 07:46 am - by RockyMtnBrain (2 Posts)
icon

Well, it looks like you got through the first 4 activities successfully (I see submissions from you for those earlier activities), so it's fair to assume that your environment is all set up and running correctly.

Is there anything printing in the Console panel in Eclipse?  Sometimes when something crashes you'll get some output in the Console window.  If so, copy/paste it here and we'll see if it makes sense.

If nothing in the Console window, you might try running the debugger.  In Eclipse, go to Window -> Open Perspective, and select Debug.  The whole look of Eclipse will change to enable debugging.  Then select Run -> Debug.  You may get output in the Console and LogCat panes. LOTS will print in the LogCat; above the LogCat pane, you can click the red E to filter it down to just Error messages. Even so, there will be a lot; I see a lot of Error messages even when the app is working correctly (I suspect just a lot of debugging output in the Android runtime that is logging at Error level, even though it isn't fatal).  Look through that error output, especially near then end when the program crashes, and see if there are any messages that might help you figure out what's wrong.  If not, you can try copy/paste the error messages here.

Finally, if you saved a copy of your work from the previous activity when the app was working for you, you might try going back to that and starting over with the work from activity 5, the Text Picker.  It's possible that you just missed something, or copied something incorrectly, etc.  It's often quicker to just go back to a known working state than to try to figure out what is wrong from a broken state.