[OpenLayers-Dev] More undefined variables on OpenLayers!

Tim Schaub tschaub at opengeo.org
Tue Mar 8 02:02:17 EST 2011


On 3/7/11 2:29 PM, Xavier Mamano (jorix) wrote:
> Hi,
>
> Using Closure Compiler is possible to have a report of all undefined
> variables.
>
> Now this is the result:
>
> ...
> ..\lib\OpenLayers\Layer\Grid.js:704: ERROR - variable tlViewPort is
> undefined
> tlViewPort = tlLayer.add(offsetX, offsetY);
> ^

http://trac.osgeo.org/openlayers/changeset/11663/

> ..\lib\OpenLayers\Map.js:1692: ERROR - variable yRestriction is undefined
> var xRestriction = yRestriction = 0;
> . . . . . . . . . .^

http://trac.osgeo.org/openlayers/changeset/11664/

> ..\lib\OpenLayers\Renderer\SVG2.js:655: ERROR - variable component is
> undefined
> component = components[i];
> ^

http://trac.osgeo.org/openlayers/changeset/11665/

> 3 error(s), 26 warning(s)

Thanks for the vigilance.
Tim

>
> (now is not possible get this report using "build.py -c closure")
>
> Xavier Mamano
>
>
>
>
> --
> View this message in context: http://osgeo-org.1803224.n2.nabble.com/More-undefined-variables-on-OpenLayers-tp6099332p6099332.html
> Sent from the OpenLayers Dev mailing list archive at Nabble.com.
> _______________________________________________
> Dev mailing list
> Dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev


-- 
Tim Schaub
OpenGeo - http://opengeo.org
Expert service straight from the developers.


More information about the Dev mailing list