Sorry I just sent "reply to author" instead of reply. The show/hide methods work on all controls, custom or documented. So if you use just documented controls, you can well use these undocumented methods.
It's just the selector elements which break in IE or Safari, and as far as I know no documented controls use selectors (anyone know for sure?) so yes, you can look at this as a custom control issue. But remember, custom controls use documented features (mine certainly do). I'm thinking it may a couple of possibilities: 1) the Selector is not put in the right layer in IE or Safari so it "blocks" the mouse from seeing the map (or actually blocks the map from seeing the mouse) so it thinks you have gone off map. I certainly use the standard conventions for adding the controls to the map, but perhaps the select list is in a different layer. 2) Maybe it's a style problem. IE is known to use non-standard styles (such as opacity) and perhaps with some funny IE style on my selector, I could be made to work. As for alternatives, I can only think of the addControl() and removeControl() methods which seem like a heavy handed (and perhaps more resource intensive) way to do it. On Dec 1, 3:58 pm, f5vag <[EMAIL PROTECTED]> wrote: > On Dec 1, 9:15 pm, Esa <[EMAIL PROTECTED]> wrote: > > > On Dec 1, 9:27 pm, f5vag <[EMAIL PROTECTED]> wrote: > > > > The safest way is to use only documented methods and to hide the > > > individual elements with own code. > > > Do you have an example. > > No, I don't use custom text controls like Papa Bear. > > GE --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
