This might be a stretch, but I do recall a scenario where changing
opacity was not working in my application and I was at one point doing
some testing with VE. To fix the problem, I reversed these lines of
code in OpenLayers.Util.modifyDOMElement in Util.js:
element.style.opacity = opacity;
element.style.filter = 'alpha(opacity=' + (opacity * 100) + ')';
Since I never isolated the source of the problem or saw anyone else
complain about it, I did not see the need to submit a patch, but perhaps
this is it. It is worth a shot...
Regards,
Jeff
[EMAIL PROTECTED] wrote:
On Sun, Nov 25, 2007 at 01:47:05PM +1100, bradleyspencer wrote:
List,
I have been experimenting with VE as an optional base layer and have
identified some real showstoppers that others may have a fix for.
If you want to allow a user to interactively modify a layer?s opacity atop
of the VE base layer, this does not work in FierFox but does in IE7. I am
using png.
This is a bug in VE's API.
Is this a bug that needs fixing or is VE not a serious option as a base map?
VE is not an option if you want to use client-side opacity.
Regards,
begin:vcard
fn:Jeff Yutzler
n:Yutzler;Jeff
org:IONIC Enterprise, Inc.
adr;dom:Suite 300;;901 N. Pitt St.;Alexandria;VA;22314
email;internet:[EMAIL PROTECTED]
title:Senior Geospatial Systems Engineer
tel;work:(703) 535-5973X17
tel;fax:(703) 535-5975
tel;cell:(703) 981-8753
x-mozilla-html:TRUE
version:2.1
end:vcard
_______________________________________________
Users mailing list
[email protected]
http://openlayers.org/mailman/listinfo/users
