Hi Jackie, thanks for your reply. I already checked all the release notes up to the current version and have made the relevant changes. I had now time to look a little closer into this problem and figured out, that there is an issue with the coordinates of the geometry and not the styling what was my first thoght.
Since the features were displayed in your codesamples up to version 4.3.4 I would assume that MapGuide delivers the geometry with the correct coordinates. In all versions higher or equal than 4.4.0 all I can see in developer tools are geometries with an array of coordinates like that: [NaN, NaN, ...., NaN]. So the number of coordinates seems to be correct while the values are not. It doesn't matter if we create features of type "ol.Feature" or "ol.render.Feature". I even have used a tileLoadFunction to get more control over what's happening. But even within in this function I'm not able to find out where the coordinates were lost. So, I wonder what can cause this loss of coordinate values. Could it be that there is something additional missing in the response from MapGuide that the newer versions of OpenLayers expects. Any idea? Thanks, Gunter -- Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
