React-Native-Maps onRegionChangeComplete Breaks & Returns (0,0) and Obscure Lat/LngDeltas -

-

some serious head-banging-on-desk action going on over here. we're using react-native-maps , it's 50/50 chance jumps map (0,0) when refreshing.

we're using onregionchangecomplete prop, , after diving deeper, we've can see it's returning incorrect lat/long/latdelta/lngdelta so....

  • latitude: 0
  • longitude: 0
  • latdelta: 102.73569069743314
  • lngdelta: 72.32139609754086

when works properly, coordinates it's bringing more like...

  • latitude: 35.78307468033585
  • longitude: 99.8066698028755
  • latdelta: .072463719198538
  • lngdelta: .051887668669237996

the person working on me having same issue same dev, with incorrect results being...

  • latitude: 0
  • longitude: 0
  • latdelta: 148.03909769956485
  • lngdelta: 126.56251475214958

when coordinates should getting like...

  • latitude: 45.06256685043254
  • longitude: -103.290462680161
  • latdelta: .0724636120368487
  • lngdelta: .056723691523089315

i've heard react-native-maps can quite buggy, can't possibly ones come across issue. i've pored on every thread can find had no luck. i'm hoping out there has had similar problem , has found fix?! thanks!!!

extra info

every time onregionchangecomplete 'breaks', no matter we've panned or zoomed to, latdelta & lngdelta returning same 2 numbers. (102.7356..., 72.3213...) me, , (148.039..., 126.5625...) partner. @ first thought because we're in different locations, no matter how manipulate map, 2 numbers don't change (only when onregionchangecomplete 'breaks', otherwise update correctly). feel there's reasoning behind 2 different sets of numbers might give answer, can't find correlation. thing think it's creating numbers based upon our differing screen dimensions. , appreciated! thanks!!


Comments

Post a Comment

Popular posts from this blog

ios - MKAnnotationView layer is not of expected type: MKLayer -

-
Image
so code works fine logger riddled message. there way rid of or suppress it? postannotation.swift class postannotation: mkpointannotation { //mark: properties let post: post //mark: initialization init(post: post) { self.post = post super.init() self.coordinate = cllocationcoordinate2d(latitude: post.latitude, longitude: post.longitude) self.title = post.title self.subtitle = post.timestring() } } adding annotation let annotation = postannotation(post: post) self.map.addannotation(annotation) func mapview func mapview(_ mapview: mkmapview, viewfor annotation: mkannotation) -> mkannotationview? { if annotation mkuserlocation { return nil } var annotationview = mapview.dequeuereusableannotationview(withidentifier: "pin") as? mkpinannotationview if annotationview == nil { annotationview = mkpinannotationview(annotation: annotation, reuseidentifier: "pin")
Read more

ZeroMQ on Windows, with Qt Creator -

-
i have installed zmq link given below on windows 7. http://zeromq.org/distro:microsoft-windows 1) have c++ project in qt-creator , i'm using zmq c++ binding (zhelpers.hpp etc). 2) have added .lib installed zmq folder qtcreator 3) while compiling, compiler looks _imp__zmq_verion, in .dll files present in .lib have __imp_zmq_version. 4) causing undefined reference zmq_version. anyone else faced problem , has solution ?
Read more

unity3d - Unity SceneManager.LoadScene quits application -

-
i have 2 different scenes 1 named 'main' , other 'game' both added scenes in load. when use scenemanager.loadscene("game"); works no problem when tried return main scene code if (input.getkeydown (keycode.escape)) { scenemanager.loadscene("main"); } strangely game quits. thanks. sorry interruption. somewhere on other script found code. if (input.getkeydown (keycode.escape)) { application.quit (); } that's bad, know...
Read more