[OpenLayers-Users] single file library distorts size of markers?

[Christopher Schmidt]

On Wed, Aug 08, 2007 at 04:04:47PM +0100, Joanne Cook wrote:
> Hi Erik,
> 
> Thanks for getting back to me. I am pretty certain that I haven't made any other changes- in fact I downloaded 2.4 to check! 
> 
> When you zoom into the 2.4 uncompressed version, do you see semi-transparent orange circles or blue info signs? I see orange dots that are nothing to do with my markers- and in fact when I check what has loaded using firebug marker.png doesn't seem to show up.

Your WFS layer is set up to be displayed as a 'vector' layer in 2.4,
because your options array is split into 3.

{scales: [500000, 10]},
        {ratio: 1.0},
        {featureClass: OpenLayers.Feature.WFS});

Those should all be parameters/ key+value pairs in the same object.

{scales: [500000, 10], ratio: 1.0, featureClass: OpenLayers.Feature.WFS});

Those 'orange circles' *are* your WFS layer, but changing it to the
above should change it to use the markers.

If you're using the 2.4 *compressed* library, built with './build.py',
by default, it does not include vector support. This means that the
vector layer would fail to draw, and you might fail back to having
markers. Which would be why uncompressed vs. compressed would behave
differently in 2.4.  

./build.py full

will build a full OpenLayers library -- with vector support -- giving
you the same behavior as uncompressed, but it shouldn't matter either
way to you once you fix your options.

Regards,
-- 
Christopher Schmidt
MetaCarta