Thank you so much Xavier. That was a bit of a silly mistake on my part. Thanks for your help ~TreKing and Mark as well. I can't believe I didn't notice that. Of course one of the biggest problems with my app is a typo. Thanks so much again! And especially thank you for the quick replies!
On Apr 23, 5:51 pm, Xavier Ducrohet <[email protected]> wrote: > The exact error is here: > > 04-23 16:46:29.079: ERROR/AndroidRuntime(216): Caused by: > java.lang.ClassNotFoundException: com.adamcarruthers.TapPlotDrawer in > loader dalvik.system.pathclassloa...@43d03158 > > but in your XML it shows a different class name: > com.adamcarruthers.multitude.TapPlotDrawer > > I'm not sure what's going on here, but you need to make sure that the > full qualified name of the class and the XML node are the same > (case-sensitive too) > > Xav > > On Fri, Apr 23, 2010 at 4:39 PM, Adam Carruthers > > > > > > <[email protected]> wrote: > > All I meant about the class inflating itself was that I noticed one > > line: > > > ((Activity)getContext()).getLayoutInflater().inflate(R.layout.mixer, > > this, true); > > > And I realize after analyzing the code a little more that you were > > inflating an XML resource. Maybe I worded my topic wrong. All I have > > is a class that I'm trying to add to main.xml with the lines: > > > <com.adamcarruthers.multitude.TapPlotDrawer > > android:layout_height="fill_parent" > > android:layout_width="fill_parent" > > /> > > > Could there be something wrong with how I'm going about doing this in > > the XML? > > > On Apr 23, 5:28 pm, Mark Murphy <[email protected]> wrote: > >> sudo.adam wrote: > >> > While working on that > >> > app did you find it necessary to have the class inflate itself? > > >> I am not sure what you mean here. > > >> > When > >> > I was going through the documentation on the dev site it seemed to > >> > just say that you have to extend a class and override a few methods to > >> > your liking. > > >> Oh, well, that's certainly theoretically possible. It all depends on > >> what you're trying to accomplish. If there's an existing View class that > >> is 99% of what you want, perhaps just a subclass and a few overrides are > >> all that's needed. > > >> In the case of the example I linked to, there wasn't really an existing > >> widget to work from, so I created one out of parts. Kind of like > >> Frankenstein. :-) > > >> -- > >> Mark Murphy (a Commons > >> Guy)http://commonsware.com|http://twitter.com/commonsguy > > >> Android Consulting:http://commonsware.com/consulting > > >> -- > >> 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 > >> athttp://groups.google.com/group/android-developers?hl=en > > > -- > > 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 > > -- > Xavier Ducrohet > Android SDK Tech Lead > Google Inc. > > Please do not send me questions directly. Thanks! > > -- > 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 > athttp://groups.google.com/group/android-developers?hl=en -- 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
