Wednesday, September 4, 2013

WhirlyGlobe-Maply 2.2 Beta

As promised, the WhirlyGlobe-Maply beta is up for version 2.2.  You can get it on github from the master branch.  That's the preferred location.

Gratuitous Image
If you want a binary distribution, I've got one of those up now too.  This includes the framework, now stripped of its debug info, as well as a the sample app and all dependent libraries.


6 comments:

  1. This comment has been removed by the author.

    ReplyDelete
  2. Hello,
    Is the NaturalEarthData app meant to be buildable at this time?
    I'm getting a lot of undefined symbols errors at the Ld stage.

    ReplyDelete
  3. Nope, I never finished that. It was meant to be a Natural Earth Data browser. I use a lot of their data set in random projects and I was putting together a little homage/shout-out.

    At this point it may reappear in a new project I'm doing, but not in this form. I'll move it to the graveyard.

    The WhirlyGlobeComponentTester is the most complete test app.

    ReplyDelete
  4. Hi again,
    I tried to use the MaplyComponent but ran into a strange error on this line:

    mapViewC = [[MaplyViewController alloc] initAsFlatMap];

    It's a runtime exception saying boolForKey:default: is an unrecognized selector for an NSDictionary instance.

    The WhirlyGlobeComponentTester test app uses the same line of code but doesn't have this problem.

    I found the NSDictionary+Stuff category which defines the selector, but I don't have a clue why the error occurs in my app. I tried including the NSDictionary+Stuff.h file before the initAsFlatMap call, but it did help.

    I did diverge from your example project in this regard: rather than including the entire MaplyComponent project within my project as a sub-project, I just added the static libraries through Build Phases / Link Binary With Libraries.

    In the short term I guess I can just copy your example project and modify it, but it would certainly be helpful if you have any tips.

    Thanks!

    ReplyDelete
  5. Be sure to include the -all_load flag in "Other linker flags"

    ReplyDelete