Excuse me for probably overlooking something simple :)
I'm trying to get semi-transparent polylines to work correctly in Firefox. At present they are showing up completely opaque in FF 1.5.0.7 and 1.5.0.8, but fine in IE7.
A sample is:
function GetMap()
{
map = new VEMap('myMap');
map.LoadMap(new VELatLong(-40.3555, 175.615), 13 ,'r');
var pl = new VEPolyline("12345",[new VELatLong(-40.3555, 175.615), new VELatLong(-40.3565, 175.655)],new VEColor(0,255,0,0.5),5);
map.AddPolyline(pl);
}
Is this an issue with FF, my svg engine, or something I've missed
Also, on a totally different note, we're porting a prototype app from GMaps, and one thing I feel is that VE methods throw exceptions unnecessarily. For instance, I discovered I was trying to delete a polyline which didn't exist. This threw an unfriendly exception and stopped the code in its tracks. The GMap equivalent, removeOverlay, doesn't seem to care if the overlay I'm trying to remove doesn't exist (in fact I discovered a nice bug in my gmap code in the process :)). Point is, it would be nice, in non-critical situations for there to be less exceptions, and more soft error handling.
ax
p.s. luv the 3d.. where is the westin hotel in atlanta :)
Polyline Opacity
Nevin
on the totally different note, you do know you can put proper try catch error handling in javascript
eg.
try {
something_with_an_error;
} catch (err)
{
alert("oops");
}
This way if you simply want to ignore the error in prod you can, but in dev it is good to know what is going on, like why you are tring to delete an object that doesn't exist.
John.
catalinione
Yes - and that was how i resolved the delete issue. Just try/catch can be slow. And adding extra code to handling the single (initial) case that was failing just didn't fit in the spirit of my elegant design :)
Still, any word, or replication, on the firefox polyline opacity