It sucks that javadoc can influence generated code. You'd think there would be
a language keyword for that.
-Original Message-
From: monodroid-boun...@lists.ximian.com
[mailto:monodroid-boun...@lists.ximian.com] On Behalf Of Jonathan Pryor
Sent: Wednesday, March 13, 2013 2:46 PM
To: Dim
On Mar 13, 2013, at 12:18 PM, Dimitar Dobrev wrote:
> OK, this makes sense. So, is it then some kind of a bug in the Android
> SDK? I don't see a reason for the android.jar on the device (or on the
> emulator in my case) to be different.
This is not a bug in the Android SDK. If you read the
OK, this makes sense. So, is it then some kind of a bug in the Android SDK?
I don't see a reason for the android.jar on the device (or on the emulator in
my case) to be different.
Dimitar
From: Jonathan Pryor
To: Dimitar Dobrev
Cc: "monodroid@l
On Mar 13, 2013, at 4:19 AM, Dimitar Dobrev wrote:
> Besides, I've already said that manual binding through JNI works (I've
> exposed just 2 fields because I only need them for now).
Your original question was regarding why it wasn't present as
global::Android.Resource.Styleable. The answer is
hi,i m doing practice on listviews concepti tried example in
http://docs.xamarin.com/guides/android/user_interface/working_with_listviews_and_adapters/part_4_-_using_cursoradaptershere
m getting error...
UnhandledException...System.NullReferenceException at
listview.Adapter = new SimpleC
Well, I am pretty sure "com.android.internal.R.styleable" and
"android.R.styleable" are the same. For example, in the same class they use the
"internal" "com.android.internal.R.attr.ScrollViewStyle" which, however, is
available in Mono for Android as Android.Resource.Attributes.ScrollViewSt
