- This topic has 43 replies, 5 voices, and was last updated 10 years, 8 months ago by
.
-
Posts
-
@pwleblanc
I started by creating a simple example that reuses a map and updates a path through the google map api. No issues observed – worked without issue. These things are hard to prove without debugging your project to isolate the issue. I’ll continue tomorrow.
Yes, but you’ve got two users reporting the same behavior. My maps go wonky when some other widget updates, for example a combo box.
> My maps go wonky when some other widget updates, for example a combo box.
Can you provide a small minimal example that demonstrates the issue you are observing? Makes it much quicker to isolate and resolve issues.
HI Michael,
Thanks so much for looking into this. Several point that might help you. The problem occcurs when I run my program on an iPhone or my iPad. I sent instructions as to what I type in and how to get the map to fail. Note, again this did not occur when compiled with 2.3, just since 2.6.** I have been previously compiling with the setting – iPhone, iPod, portrait – and the problem exists. Last night I decided to try compiling using the option – universal ie iPhone,iPod,iPad, -….. Believe it or not the maps now work on the iPhone !!! So it has to be something with the compile in 2.6.
You had said they changed – in 2.6 – something about how mobione stored map info so people could turn off their device and the map would refresh as before when they turned it back on. Could you take this function out of 2.6 and test and see if the maps then work in my program? this would be an easy way to isolate the problem. I think we are narrowing it down – hopefully!!
Note: I have tried a small map program too and the maps function correctly, but not in my large program. Yopu have all my code.
Thanks,
PaulTesting my app more, it seems that the map error occurs when I write to localstorage, after the map is initiated. I write a variable named “radius”. Is the map widget also trying to write a “radius” to localstorage?
>Is the map widget also trying to write a “radius” to localstorage?
The map widget caches its geocoded location property to local storage.
Without an example that replicates the issue can’t say if this is an issue or not. In your project you can try removing the location property and thus no local storage read/write by the widget and see if your issue resolves.spoke too soon. When I compile in the – universal – mode map works ok on the iPad, but not correctly on the iPhone.
The error only happens when I write “radius” to localstorage, not other variables. Let’s rename “radius” and see what happens.
>When I compile in the – universal – mode map works ok on the iPad, but not correctly on the iPhone.
I tried a few diff mods on your use the google map api with no success. I don’t know the cause yet. I discussed with a developer. We saw something like this when the map was initialized before the containing element. This caused the map to be much smaller than the container. Is that happening here? I can’t say but I don’t think so.
What is odd is there is this can only be replicated on a device (I am able to replicate it on ipad & iphone). I recall there are different map api implementations loaded based on the device.
The example I created yesterday similar to your app contains multipages with a map that is updated from 3 diff sources with markers and maps. I was looking for some direct failure but no success. So I have not isolated the cause (1st step to resolution). Will try some other things. Will continue investigating and hopefully can narrow it down.
OK after a long process of elimination I have a small example that replicates the issue on ios devices. I have kicked it over to dev to analyze. I don’t believe it is localstorage related as I removed all of the caching and it still does not render correctly.
I can confirm that writing “radius” to localstorage is not what causes the map to go wonky. I changed my localstorage variable to “my_radius” and it still goes faulty.
In my app, the map goes wonky when: I use a combobox to choose radius, then write that number to localstorage. Changing radius seems to be the issue with the map. The “center” of the map (user coordinates) become the upper-left-hand-corner coordinates.
-1TC
@pwleblanc @thinchip
Update, good news with your feedback and some late night work this weekend our lead dev isolated the issue. I just saw the fix for the map widget go into the code stream. OC or I will update you as soon as we have a target date for the next mobione update (I think it will be 2.6.2). If you’re interested we can provide a dev build that will include the fix later today or tomorrow timeframe once it goes through testing and verification.
