Hi Scott. Take a look at this version of your page:
http://code.martinpearman.co.uk/deleteme/GMap1.html I'm 99% sure you don't need the loadDelay() function as the initialize() function only executes once the entire page has loaded - whether the page is viewed directly or within an IFRAME i don't think you need that delay. And the line: google.load("maps", "2.x"); Is not required either - the API loads via the SCRIPT element with the API key. Putting the height:100% CSS rule in an inline STYLE element means the page now validates: http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fcode.martinpearman.co.uk%2Fdeleteme%2FGMap1.html Your version of the page has some errors - whether one or more of these errors stopped the map displaying full 100% size i don't know: http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fmysite.verizon.net%2Fvzenti29%2Fpublic_html%2FGmap1.html Martin. On 22 Aug, 18:59, ScottE <[email protected]> wrote: > Hi guys, > I spent some more time working with the Econym example Martin > recommended and made some real progress just by playing with the Gmap > code and doing nothing with the styling. Updated Gmap: > > http://mysite.verizon.net/vzenti29/public_html/Gmap1.html > > Emulating the Econym map's earlier body and div was kind of tricky for > me (and I realized naming the div element "map3d" or "map" etc is > arbitrary). As you can see the width is now 100% and the map outputs > flush with the browser window edge widthwise (it's that way in the > iframe too; a major improvement), but 100% height doesn't work for my > map like it does on the Econym example. If I use Econym's code, 100% > height in the div ends up perfectly flush at top and bottom. Not so in > my map — still some padding at top and bottom, and a vertical scroll > bar. Any ideas what I'm doing wrong? > > As a workaround, I can set the div height to 90%, which creates a bit > more padding, but removes the scroll bars completely. (Still a major > improvement.) > > By the way, the first timeout in my code is for accommodating the > iframe load and the second allows time for the GEarth layers to load. > I also tacked in a map.checkResize(); after the GEarth functions — > without it, for some reason, sideways/width scrollbars appeared when > switching from the GEarth layer to a regular map within the iframe. > > And unlike the Econym map, I added <body onload="initialize()" to this > line: <body onload="initialize()" onunload="GUnload()" style="height: > 100%;margin:0"> > Seemed liked the most proper way to do it. I tried it with and > without, and it didn't seem to make a difference, but is the > intitialize() in that line perhaps redundant? > > Thanks a lot, > Scott > > On Aug 19, 3:22 pm, ScottE <[email protected]> wrote: > > > Thanks a lot Mike and Martin. > > I tried out Martin's first idea based on the econym code but no luck. > > It could be because I'm using a GEarth layer and map = new > > GMap2(document.getElementById('map3d') instead of the simple "map" (I > > remember "map" never worked with GEarth for me). But it could be many > > other things. > > > I'll keep playing with that and I'll try the CSS andiframeparameters > > angles too. If this matters, the Gmap code is linked to from within a > > div on the parent page, and theiframeis being created by Thickbox. > > Thanks again guys. > > > If anyone else has other ideas, or would like to chime in about the > > ones above, please do. I really appreciate the help. > > Scott > > > On Aug 19, 1:51 pm, Mike Williams <[email protected]> wrote: > > > > In the parent page use the following parameters inside the <iframe> > > > call. > > > > scrolling="no" > > > marginheight="0" > > > marginwidth="0" > > > frameborder="0" > > > > -- > > > Mike Williams -- 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.
