Sorry about my last incomplete message.
On Dec 4, 1:18 pm, teknocreator <[email protected]> wrote:
> Bratliff - I can't post a link just yet due to restrictions on the web
> server I work with. However, I'll post more and probably some code
> after I see about experimenting more with CANVAS and using what you
> sent. I don't want info on Google's images/maps, but the overlays I
> create. After working with this for a bit now, I'm actually surprised
> more properties/methods aren't available with the overlays. To me
> there should be built in methods to control the opacity (had to cobble
> something together for that) and also gleam information from them. Or
> at least somehow build a legend based on them (maybe that's out there
> and I just haven't gotten there yet). Otherwise (and especially
> without opacity), they're just something to look at while covering up
> other information you might want to see at the same time (i.e. GM Map
> Types).
You can control opacity quite easily. Generate your PNGs at your
server with an alpha component between 0 and 255. Assuming your PNGs
are contained in a DIV, you can assign "opacity" to its "style". The
actual name may be different among browsers. For Internet Explorer,
you will have to use the "alpha" filter.
> I think IE 9 is supposed to support CANVAS, but it's still in beta.
> There is a work around JS script file called excanvas.js. But, it
> doesn't contain some of the functionality needed with CANVAS and I've
> also read that certain operations can really slow down a page.
Unfortunately, excanvas.js just translates CANVAS to VML. It has a
lot of stuff you may never use. If VML does not support a particular
feature, excanvas.js will not be able to support it either. I am not
aware of VML equivalents for the methods:
drawImage
getImageData
putImageData
> If CANVAS doesn't work, there are a few other things I might be able
> to do. The server-side mapping suggestion may be something to check
> into. If a user clicks to retrieve on the map, server retrieves info
> at that point from the overlay field info that would be stored on the
> server. Maybe create an info window at user click location with the
> overaly info. It wouldn't be realtime sampling with the mouse, but it
> would allow a user to get some useful info about the overlay field.
> Just thinking outloud.
KmlLayers use an auxilliary support structure for clicks and cursor
changes. Perhaps Ben Appleton can explain. You might be able to do
something similar.
--
You received this message because you are subscribed to the Google Groups
"Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
