What's odd is that I check the annotation array for nil termination earlier on
and to alert me.
No alerts.
But I do a check when rebuilding the array to ignore nil results and that
exports fine.
I'm still thinking that nil termination is creeping in there but all I have
inside are locatio
On 22 Apr 2012, at 6:51 AM, Uli Kusterer wrote:
> It could be a CFArrayRef. CFArrayRef can handle *any* kind of pointer for its
> values, if you give it the right callbacks, and it's toll-free-bridged to
> NSArray. Of course, if you try to get an object out of it and it actually
> contains some
On 19.04.2012, at 19:39, Fritz Anderson wrote:
> This confuses me. MKMapView.annotations is an NSArray. How can an NSArray be
> nil-terminated? It has a count and there's no way to index into it that would
> return anything but an object. There's no need and no way to terminate it.
>
> (...) If,
On Apr 19, 2012, at 1:39 PM, Fritz Anderson wrote:
> On 19 Apr 2012, at 12:01 PM, Alex Zavatone wrote:
>
>> Yeah, it was the fact that the CLLocationDegrees in the
>> CLLocationCoordinate2D struct were doubles, or that CLLocationCoordinate2D
>> was a struct.
>
> Likely both. structs are not w
On 19 Apr 2012, at 12:01 PM, Alex Zavatone wrote:
> Yeah, it was the fact that the CLLocationDegrees in the
> CLLocationCoordinate2D struct were doubles, or that CLLocationCoordinate2D
> was a struct.
Likely both. structs are not wrapped NSNumbers, NSStrings, NSArrays,
NSDictionaries, or NSNul
Yeah, it was the fact that the CLLocationDegrees in the CLLocationCoordinate2D
struct were doubles, or that CLLocationCoordinate2D was a struct.
The other possibility might be if the mapView.annotations array is nil
terminated, that might cause the premature death.
Rebuilt the string and recre
Thanks. Might be the annotation coordinate list then.
The MapKit annotation list entries use CLLocationCoordinate2D of
CLLocationDegrees for long and lat.
Xcode straight out SIGABRTs when trying to convert the mapView.annotations.
Looks like I'll have to convert those location Degrees to NSSt
On 19 Apr 2012, at 9:14 AM, Alex Zavatone wrote:
> I'm wondering if there are any hard and fast basic rules on why an
> NSDictionary or NSArray would not be pass the [NSJSONSerialization
> isValidJSONObject: jDict]
> test.
>
> According to the docs, isValidJSONObject:, returns a Boolean value t
I'm wondering if there are any hard and fast basic rules on why an NSDictionary
or NSArray would not be pass the [NSJSONSerialization isValidJSONObject: jDict]
test.
According to the docs, isValidJSONObject:, returns a Boolean value that
indicates whether a given object can be converted to JSON
