Thanks Mel
I'm pretty sure the problem I saw was definitely occurring inside the app.
The debug trace for the location was fine, but the object properties were
garbage. This was in the OnLocationChanged handler from the LocationManager
- so only one call stack frame away from the Java, and nowhere
Hi
On 2012.02.06 16:39, Stuart Lodge wrote:
The values were wrong in debugger and in Trace.
What's more I also got corruption on other local "stack" variables -
e.g. if I copied the values to a locally new'ed class, then that class
also had issues.
This problem persisted for about 3 hours -
The values were wrong in debugger and in Trace.
What's more I also got corruption on other local "stack" variables - e.g.
if I copied the values to a locally new'ed class, then that class also had
issues.
This problem persisted for about 3 hours - I tried clean builds and phone
and PC reboots - n
Is this just in the debugger?
If you use something like Console.WriteLine are the values correct?
Jonathan
On 2/6/2012 5:42 AM, Stuart Lodge wrote:
I'm looking at some Location traces right now where the
Andtroid.Locations.Location object has good mLatitude and mLongitude
private values, but h
I'm looking at some Location traces right now where the
Andtroid.Locations.Location object has good mLatitude and mLongitude
private values, but has seemingly garbage public Latitude and Longitude
property values
For example. the debug trace for the object is:
{Location[mProvider=network,mTime=13
