Another way to darken the map would be by setting an opacity style either on
the element id="map_OpenLayers_ViewPort" element if it should darken the
controls as well or on the element id="map_OpenLayers_Container" if the
controls should remain fully visible. I haven't checked by I think that the
I was *em* debugging with the old alert right before the offending statement
which made the problem go away. So I tried at the start of the VML.js file.
Worked too. But I don't like to modify the OpenLayers files so I tried
before the Ext.onReady definition... Then I got rid of the alert. I ended
I'm using Ext.js and got the same problem for a script running in the
Ext.onReady function call which is supposed to run before the onload event.
I just put the following line before the definition of that function and I
didn't get the error anymore.
document.namespaces;
Ext.onReady(.);
--
I think I've found part of the problem:
in Layer\GML.js, function requestSuccess, the following line:
if (!doc || request.fileType!="XML") {
always have the second part true since 'request.fileType' is not defined (at
least when running in IE7). Changing it to
if (!doc) {
solves the problem.
Lourens Veen-2 wrote:
>
> ...I've changed the WFS class to accept a "filter" option to which you can
> add an OGC Filter XML filter specification fragment. If you don't, then
> the code will send the BBOX constraint as before, if you do then it
> will combine the fragment with an XML descript
Ryan Hofschneider-2 wrote:
>
> available, you might get an error from your WFS server because
> WFS.moveTo() will add a BBOX parameter to the request URL which is
> supposed to be mutually exclusive with the FILTER parameter. At least
> this is my experience when using OpenLayers with GeoS
