> Proposed feature: Always call onMarkersSetCallback, after all
> "zero markers were set" can be also an interesting event.
Horror workaround in the onSearchComplete callback:
[...]
if ( ! search.results || search.results.length == 0 )
{ setTimeout( this.patch, 100 );
this.gmap.setCenter( this.home, this.zoom );
}
_IG_AdjustIFrameHeight();
}
MapGadget.prototype.patch = function()
{ var chi = 10; // patch "no result" row in
var rel = _gel( "res" ); // fresh gmls-results-table:
while( rel && rel.firstChild && --chi ) rel = rel.firstChild;
if ( ! chi )
{ rel.style.cssFloat = "left"; // get branding on same line
rel.style.display = "inline"; // patch "none" set in CSS
rel.parentNode.appendChild( GSearch.getBranding());
_IG_AdjustIFrameHeight();
} }
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
