Actually javadocs in droiddoc format has to be passed as DroidDocPaths
property, not JavaDocPaths property which is to parse HTML in default
javadoc format (I believe this is the default, and consistent, but there
is no assurance that java sdk doesn't change the format).
Atsushi Eno
Jonathan
That rather sounds like your class misses some required callback class
that Java code requires in certain name, and your Tab implementation
needs to use ExportAttribute which was introduced in MfA 4.2 (actually
4.1 preview).
I wanted to point to our documentation, but it seems our doc team
so
Are you sure? I generated docs using Javadoc and passed them in JavaDocPaths.
That did not work.
Then I regenerated the bindings using doclava and passed them as JavaDocPaths
and it sort of worked (some of the method names changed but I don't see any of
the comments).
Jeremy
-Original M
I have an application targeting api level 15, and I noticed that
LocationManager.requestSingleUpdate() seems to be missing. Am I missing
something, or is this not implemented? And are there plans to implement it?
I'm running Mono for Android 4.2.6.
Thanks,
Andy
--
View this message in contex
On Oct 12, 2012, at 12:09 PM, andyjohnson0 wrote:
> I have an application targeting api level 15, and I noticed that
> LocationManager.requestSingleUpdate() seems to be missing.
It's bound; you need to target API level 9 or later:
http://androidapi.xamarin.com/?link=M%3aAndroid.Locatio
Ok I figured out how to get the javadocs working (it turns out doclava made
things worse). So now I get parameter names but I don't see the
"documentation" portion just as what the method does etc. Can the tool extract
that information as well?
-Original Message-
From: monodroid-boun.
On Oct 12, 2012, at 1:30 PM, "Jeremy A. Kolb - ARA/NED" wrote:
> Ok I figured out how to get the javadocs working (it turns out doclava made
> things worse). So now I get parameter names but I don't see the
> "documentation" portion just as what the method does etc. Can the tool
> extract tha
