[mapserver-dev] 6.2 release notes/announcement

Alan Boudreault aboudreault at mapgears.com
Wed Nov 14 06:06:50 PST 2012

I confirm yes. There is no more label property in the classObj. Users 
have to explicitly use addLabel, getLabel and setLabel.


On 12-11-14 08:56 AM, thomas bonfort wrote:
> Daniel,
> I have added your suggestions to the repo, they should appear shortly.
> I'll let Alan or Alexandre amend if needed, but will be announcing the
> release on our mailing lists in the coming hour anyways.
> cheers,
> thomas
> On Wed, Nov 14, 2012 at 2:44 PM, Daniel Morissette
> <dmorissette at mapgears.com <mailto:dmorissette at mapgears.com>> wrote:
>     there is at least one incompatibility that has been encountered with
>     MapScript vs the support for multiple label objects in a class. In
>     6.0 and older, label was an immutable member of the class object,
>     and a single label was always allocated as part of the classObj. In
>     6.2, there is no label allocated in the class object by default and
>     your MapScript code (python, etc.) has to create new label objects
>     and add them to the class object. Three new methods were added to
>     the classObj in MapScript to handle this: getLabel, addLabel,
>     removeLabel. Existing scripts need to be updated or risk silent
>     failures as SWIG MapScript (at least in python) does not complain on
>     invalid access to the label member of the classObj.
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev

Alan Boudreault

More information about the mapserver-dev mailing list