Hi Jeremy- I investigated this further, and in my experiments, allowSetVisibility is indeed defined on custom GControl extensions (for example, DragZoomControl). Can you link to your code so I can see how it's extending GControl?
Thanks! - pamela On Wed, Jan 28, 2009 at 4:23 PM, pamela fox <[email protected]> wrote: > Hi Jeremy- > > Thanks for the post. We looked into it, and realized that we should > fix our code to not assume that allowSetVisibility is defined - > instead of making developers define it. I've filed a bug internally; > feel free to file externally if you're keen to track its progress. > > - pamela > > On Tue, Jan 20, 2009 at 12:22 AM, jgeerdes <[email protected]> wrote: >> >> For the past several days, I have been trying to build a custom >> GControl running that would, among other things, open a maximizable >> GInfoWindow to display information directly on the map. Unfortunately, >> every time I included a GInfoWindowOptions argument in the appropriate >> calls, the API would throw an error: "d.control.allowSetVisibility is >> not a function." (Please note, the d is obfuscated, so it will >> periodically change.) And the infowindow, while it would open, would >> never be maximizable. After tinkering with it for some time, I >> realized that the API is looking for a .allowSetVisibility method on >> the custom control. Once that was added, the script seems to behave >> as expected. >> >> Here is why I post: In searching the various materials regarding >> custom GControls, the only mention of an .allowSetVisibility method >> that I found was on mapki, where it was noted as a new method of >> GControl. I did not find anything saying that it was a required method >> of my custom GControl, and it did not appear to be one until I >> attempted to use the maximizable InfoWindow on the map. Without that >> method, though, maximized InfoWindows are a no-go. >> >> So, for anyone out there wanting to do something similar (or even just >> build a custom GControl that might be used on a page that includes a >> maximizable InfoWindow), you will probably want to add >> an .allowSetVisibility method to your control prototype. Perhaps >> Pamela and the GMaps team might consider documenting this semi- >> required method a little better? >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
