Robust because the location manager may not have a location still after 1
second. It probably will but it might not.
--
M E R Goulding
Software development services
mergExt - There's an external for that!
On 06/02/2013, at 7:00 PM, Scott Rossi <sc...@tactilemedia.com> wrote:
> Why is locationChanged more robust than directly querying the sensor?
>
> Anyway, the issue still seems to be the same. The devices running iOS
> 5.1.1 display no data while the iOS 5.1 device does.
>
> Regards,
>
> Scott Rossi
> Creative Director
> Tactile Media, UX Design
>
>
>
>
> On 2/5/13 10:41 PM, "Monte Goulding" <mo...@sweattechnologies.com> wrote:
>
>> Why not handle locationChanged? Much more robust than waiting 1 second.
>>
>> --
>> M E R Goulding
>> Software development services
>>
>> mergExt - There's an external for that!
>>
>> On 06/02/2013, at 5:35 PM, Scott Rossi <sc...@tactilemedia.com> wrote:
>>
>>> mobileStartTrackingSensor "location", false
>>> wait 1000 millisecs with messages -- IMPORTANT
>>> get mobileSensorReading("location", false
>>
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
