ios - Center MKMapView on userLocation (initially) - only works on iPhone 4? -

-

i implemented following mkmapview method, runs after annotations added. have mkmapview map (parishmap) set "shows user location" in interface builder, , upon loading mapview, blue dot appears within second or on mapview.

here's code have in map view controller implementation:

// center map on user location (initially) - (void)mapview:(mkmapview *)mapview didaddannotationviews:(nsarray *)views {     for(mkannotationview *annotationview in views) {         if(annotationview.annotation == parishmap.userlocation) {             mkcoordinateregion region;             mkcoordinatespan span;              span.latitudedelta=0.03;             span.longitudedelta=0.03;              cllocationcoordinate2d location=parishmap.userlocation.coordinate;              location = parishmap.userlocation.location.coordinate;              region.span=span;             region.center=location;              [parishmap setregion:region animated:true];             [parishmap regionthatfits:region];         }     } }

when open mapview on iphone 4, mapview (and immediately) moves center on userlocation dot. however, when open mapview on iphone 3gs or ipod touch (2010), doesn't center on userlocation, stays @ default zoom/region set map view.

any ideas why code won't work non-iphone 4 devices (they're running 4.2.x latest ios)?

this issue amount of time takes gps lock position on these different devices.

i'd recommend using cllocationmanager , delegate methods center map.

you can start updating location creating instance of cllocationmanager, setting delegate property self , implementing:

- (void)locationmanager:(cllocationmanager *)manager didupdatetolocation:(cllocation *)newlocation fromlocation:(cllocation *)oldlocation

where can center map accordingly based on latest location update.


Comments

Post a Comment

Popular posts from this blog

Javascript line number mapping -

-
magically formatted comments change reported line number of javascript errors in browsers; this: //@line n "f" n line number , f file name. unfortunately, //@line appears ungoogleable. know there documentation on feature, , browsers support it? (i found references here , here .) from can find available in mozilla based browsers. it using js_setoptions command can turn these options on or off depending on values passed. https://developer.mozilla.org/en/js_setoptions
Read more

linux - Mailx and Gmail nss config dir -

-
i trying send mail linux command line using mailx command. can send local domain no problem want set mail send gmail account receive mail sent gmail account. after configuring mail.rc so: account gmail { set smtp=smtps://smtp.gmail.com:587 set smtp-auth=login set smtp-auth-user=username@gmail.com set smtp-auth-password=password set ssl-verify=ignore } i error: resolving host smtp.gmail.com . . . done. connecting 74.125.25.109 . . . connected. missing "nss-config-dir" variable. "/home/username/dead.letter" 11/354 . . . message not sent. after looking "nss-config-dir" here , located certn.db , keyn.db files , added mail.rc so: account gmail { set smtp=smtps://smtp.gmail.com:587 set smtp-auth=login set smtp-auth-user=username@gmail.com set smtp-auth-password=password set ssl-verify=ignore set nss-config-dir=/home/user/.mozilla/firefox/location.default } now when try send mail using command: echo "sent gmail account" | mailx -v -a
Read more

c# - Is it possible to remove an existing registration from Autofac container builder? -

-
something along lines: builder.registertype<mytype>().as<itype>(); builder.registertype<mytype2>().as<itype>(); builder.deregistertype<mytype>().as<itype>() var container = builder.build(); var types = container.resolve<ienumerable<itype>>(); assert.istrue(types.count == 1); assert.istrue(types[0].gettype == typeof(mytype2)); scenario: go through bunch of assemblies , go register types want make sure have 1 implementation of given type. need before create container. track on own nice if autofac me bit. this cannot done directly using containerbuilder , unless start on new one. mind you, having first built container should able construct new container filtering away unwanted types , reusing registrations first container. this: ... var container = builder.build(); builder = new containerbuilder(); var components = container.componentregistry.registrations .where(cr => cr.activator.limittype != typ
Read more