I put Members editing on, so Mike's a go. You can post that other GMarkerManager bug and I'll take a look at it- perhaps just say that it's currently not reported to the dev team, as far as I know.
On Feb 6, 1:05 am, Mike Williams <nos...@econym.demon.co.uk> wrote:
Added possible bug for encoding/decoding polylines where the encoded string includes a backslash. Google's polylilneutility page copes with this, but the API doesn't at the moment.
Thanks Mike. It's possible not all GGeoXML changes have been integrated into the current version 2.78 of the API. The engineer is looking into it right now.
- pamela
On Apr 10, 11:37 pm, "Econym" <nos...@econym.demon.co.uk> wrote:
<api.pamela...@google.com> wrote: > Thanks Mike. It's possible not all GGeoXML changes have been > integrated into the current version 2.78 of the API. The engineer is > looking into it right now.
> - pamela
> On Apr 10, 11:37 pm, "Econym" <nos...@econym.demon.co.uk> wrote:
> > Possible extremely serious bug in v2.78: GgeoXml doesn't work.
> > Please don't go live with this version until this bug is investigated.
is this a bug? both the GMarkerManager and the open source MarkerManager reveal markers that were previously hidden using the marker.hide() function when manager.refresh() is called. is there a way around this without just having to deal with it and re-hide the markers? i'd like to keep adding markers to the manager (i have to refresh) and still keep the ones that are hidden invisible. thanks in advance for any suggestions.
Hi Arno, That's expected behavior. The marker manager calls removeOverlay and addOverlay when the visible area changes, so it's completely removed the marker that you've called .hide() on before it re-creates it. It doesn't keep track of the fact that you've hidden it (it was created before .show() and .hide() were exposed, so it wasn't an issue in the past).
What are you hiding the markers for? Perhaps if you can explain the use case, I can tell you the best way of implementing it.
On Apr 17, 12:50 pm, Arno <arno.rich...@gmail.com> wrote:
> is this a bug? > both the GMarkerManager and the open source MarkerManager reveal > markers that were previously hidden using the marker.hide() function > when manager.refresh() is called. is there a way around this without > just having to deal with it and re-hide the markers? i'd like to keep > adding markers to the manager (i have to refresh) and still keep the > ones that are hidden invisible. > thanks in advance for any suggestions.
i am currently working on a restaurant guide, possibly international, where every restaurant is represented by a marker. since users are allowed to add their own restaurants i may have to display quite many at a time. that's why i decided to use the marker manager. every restaurant can have tags or categories and i would like to be able to dynamically sort the markers like "only show markers tagged with 'steak' ". that's when i'd like to hide all markers except the ones with the keyword 'steak'.
since i can't expect this possibly large amount of markers all at once, i have to keep adding markers dynamically, thus refresh the manager during runtime.
i'll try and work with mikes solution for the time, but if you have any thoughts on how this could be achieved easily and without hacks i would greatly appreciate you sharing them with me. i'll let you know how it works out. thanks again.
i've tried your solution, it seemed perfect for the job. unfortunately it just doesn't do it. i have no clue why the markers show up on the map again after a marker.refresh(). i checked and the 'isHidden' status correctly shows that the marker should be made invisible by the addOverlay_ function. only that it's not. almost as if the manager just didn't accept the hide() function existed.
i use the latest API (2.x) and if i don't use the manager, hiding and showing works perfectly. do you have any thoughts on that? i'd appreciate them very much.
I'm having the exact same problem with hidden markers, plus (and this is probably related) if I change the zoom level via the UI, all of the hidden markers suddenly re-appear! I modified the weather map example to show these bugs:
In the first, I added my API key, made the icon locations a fixed reference, and after each marker was created I called hide(). When mgr.refresh() was called, all the of icons were visible. (I did not check the isHidden status.)
In the second, I made batch[] a global variable, so I could access the contents later, and I only set up one group of icons, so batch[] was not clobbered. I also specified minzoom of 0 when adding to marker manager.
After mgr.refresh() was called, I stepped through batch[] and called hide() for every icon. That works (if a bit inefficient) when the page is first loaded, but zoom in or zoom out and voila--all of the icons are displayed.
I've confirmed this on both Firefox 2.0.0.1 and IE7 (v7.0.5730.11). I tried both v=2 and v=2.x with no change.
I'm not sure if the bug is related to the markermanager or the hide/ show functions, but either way if I hide a marker I'd like it to stay hidden. :-) Thanks, -Gregg
On Apr 24, 8:01 pm, Mike Williams <nos...@econym.demon.co.uk> wrote:
FYI, for my mash-up, when the user clicks on a radio button, certain markers are displayed and the rest are hidden. However, many markers are relevant to two or more radio buttons, and I didn't want to create a duplicate marker for each radio button. Nor did I want to have a lot of logic to say "is this loaded yet? is this currently displayed?" Thus, I created all of the markers at once, and then used hide/show to control which ones were displayed.
I can get rid of the marker manager -- I only have about 200 markers -- but I take exception to Pamela's comment that the marker manager ignoring the hidden status is "expected behavior." As a reasonable person, I certainly would not expect it to work that way. It doesn't matter what the marker manager does behind the scenes, or which was created first, it's still a bug, and a pretty serious one at that. :-( -Gregg
I added the Scroll-wheel zoom issue...I'm not sure how big/important a bug it is, but imho it is nonetheless a bug. I've found one or two reports of this problem around the web, though they are few and far between. At the very least I feel this behaviour deserves a documentation mention (i.e. don't just always all enableScrollWheelZoom(), always check if you *need* to call it first)
I apologize if I've posted my bug incorrectly - as you can probably tell, I'm new to these here boards, although I've been quietly mashing up maps for a while. If it's impolite to post one's bug first, or if I've made some error in my posting, or if the issue has already been adressed and I've missed it, please edit the list, or let me know.
