Dann, Thanks to everyone for discovering the cause and releasing the fix so rapidly.
Gary On Jan 27, 10:30 am, Daniel Lee <daniel...@google.com> wrote: > Hey Gary, > > We spent some time over the last few days debugging your application. > Eventually Susannah was able to track down the bug causing your app to > misbehave. This fix was checked in and pushed out last night as part > of the new release, which would explain why things are working again. > > Thanks for working with us to troubleshoot the issue. > > Esa, I posted an update to the 'size' option issue. Take a look and > let me know if you have any > questions.http://code.google.com/p/gmaps-api-issues/issues/detail?id=1997 > > Thanks, > > Dann > > On Jan 27, 9:42 am, Gary Little <g...@luxcentral.com> wrote: > > > > > Dann, Susannah, > > > I've re-verified the real estate map this morning and all is well. > > Whatever changes were made yesterday fixed the problems that caused my > > map to misbehave. > > > Gary > > > On Jan 26, 10:10 pm, Gary Little <g...@luxcentral.com> wrote: > > > > Dann, > > > > The map seems to work with the new version that went live at 9:44 pm > > > (see Susannah's post above), so perhaps the problem has been > > > corrected. > > > > I'll take another look in the morning. If the problem reappears I'll > > > give you more detailed instructions... and whittle the code down to a > > > bare minimum. > > > > In a nutshell, though, when you pan the map, any properties that lie > > > within the central red box are loaded from a database and should > > > appear on the map right away. The map is working as expected right > > > now, but it did not work with the previous two attempts at pushing a > > > new release -- the new markers that were loaded were not appearing > > > until the next pan was started. > > > > Gary > > > > On Jan 26, 1:28 pm, Daniel Lee <daniel...@google.com> wrote: > > > > > Hey Gary, > > > > > I'm still a bit confused as to what the expected behavior should be. > > > > > Can you provide some screenshots to help explain? In my tests, I'm > > > > seeing markers only displaying within the bounding box ever after > > > > panning from the initial load. > > > > > I have to ask again because your example contains a lot of moving part > > > > which makes it difficult to debug. Can you find a way to reproduce > > > > this in a much more isolated example? I created my own example which > > > > creates, plots, and toggles markers on a map, but it seems to work > > > > fine. > > > > > Thanks, > > > > > Dann > > > > > On Jan 25, 4:38 pm, Gary Little <g...@luxcentral.com> wrote: > > > > > > Dann, > > > > > > I was using an Apple Safari browser (on Mac and iPod Touch). Can't > > > > > test on other browsers right now because everything works once again! > > > > > However, I'm pretty sure it misbehaved on all 11 browsers I use the > > > > > last time this happened. > > > > > > Note that the initial batch of markers in view did appear as expected. > > > > > It was only after a pan that the new group of markers failed to appear > > > > > right away. > > > > > > And yes, I did verify that the POST request was working successfully > > > > > and that markers were being created after the load. It appears that > > > > > the call to setVisible on the newly created marker(s) was simply not > > > > > working... or the change in visibility was deferred until the next pan > > > > > attempt. Very odd. > > > > > > I'll try your two suggestions if I see this problem again. > > > > > > Gary > > > > > > On Jan 25, 3:23 pm, Daniel Lee <daniel...@google.com> wrote: > > > > > > > This latest version was recently reverted for reasons unrelated to > > > > > > your issue. This would explain why your production map started > > > > > > working > > > > > > again. In the meantime, we're actively working on resolving your > > > > > > problem. > > > > > > > Thanks for sharing the uncompressed code Gary. I attempted to > > > > > > reproduce the error you with your test app against the new version > > > > > > but > > > > > > was unable to do so. On the initial load, all markers within the > > > > > > bounds are successfully displaying. > > > > > > > What browser are you testing in? > > > > > > What did you see when initially loading the app for the first time? > > > > > > Were there any markers appearing on the map at all? > > > > > > Did you verify your initial POST request was returning back a > > > > > > response? > > > > > > > Some other things to try: > > > > > > - Within function M(), try setting Marker visibility to "true" by > > > > > > default. See if this has any effect. > > > > > > - Within function M(), try using default custom marker icons, i.e. > > > > > > comment out "icon: iconURL" > > > > > > > Thanks, > > > > > > > Dann > > > > > > > On Jan 25, 12:46 pm, Gary Little <g...@luxcentral.com> wrote: > > > > > > > > I've further simplified the code, so take a look. > > > > > > > > On the other hand, a few minutes ago the production map started > > > > > > > working again as expected. Google reverted?... or fixed something? > > > > > > > > Gary > > > > > > > > On Jan 25, 11:24 am, Daniel Lee <daniel...@google.com> wrote: > > > > > > > > > Hey Gary, > > > > > > > > > Your example is a bit complex with many moving parts. Were you > > > > > > > > able > > > > > > > > to reproduce this on a simpler map example? > > > > > > > > > Are others also experiencing similar problems with missing > > > > > > > > markers on > > > > > > > > the initial load? I'll mock up a test page on my own to verify > > > > > > > > in the > > > > > > > > meantime. > > > > > > > > > Thanks, > > > > > > > > > Dann > > > > > > > > > On Jan 24, 11:03 pm, Gary Little <g...@luxcentral.com> wrote: > > > > > > > > > > I'm experiencing the very same problems as with your last > > > > > > > > > attempt at a > > > > > > > > > new release: My map athttp://imap.garylittle.ca/doesnotupdate > > > > > > > > > property when the map is panned. New property markers that > > > > > > > > > come into > > > > > > > > > view are supposed to appear on the first idle event after the > > > > > > > > > pan. > > > > > > > > > Instead they show up only when the SECOND pan begins! > > > > > > > > > > Gary > > > > > > > > > > On Jan 24, 9:52 pm, "Susannah (Google Employee)" > > > > > > > > > > <susann...@google.com> wrote: > > > > > > > > > > We have just released a new version of the JS v3 API. If > > > > > > > > > > there are no > > > > > > > > > > major issues, we will make a full announcement of this > > > > > > > > > > release, with > > > > > > > > > > updated documentation, in 24-48 hours. Please report in the > > > > > > > > > > group if > > > > > > > > > > you see any regression issues. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api...@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
