[Qgis-developer] deselecting features - last minute API change?
Marco Hugentobler
marco.hugentobler at karto.baug.ethz.ch
Tue Dec 2 03:14:50 EST 2008
Hi Borys
This change does not affect API compatibility for plugins and 3rd party apps.
Please go ahead and add the QgsVectorLayer::deselect method to trunk.
>We can
> wait with gui behaviour changing for 1.0.1
+1, since we are in GUI and string freeze for 1.0
Regards,
Marco
On Tuesday 02 December 2008 01:41:43 Borys Jurgiel wrote:
> Hi,
> We can freely add vector features to selection (as well with gui as api)
> but can't deselect any feature. It's not a problem for plugins - they can
> remove selection and select again. But the problem is bigger for user who
> wants to select "all except something" or just has selected one bridge too
> far. I can imagine a number of future plugins dependent on manually
> selected features, so the ability of deselecting features is quite
> important.
>
> The reason is that we haven't any 'QgsVectorLayer::deselect' method. We
> have the following:
>
> QgsVectorLayer::select (in various variants)
> QgsVectorLayer::invertSelection
> QgsVectorLayer::removeSelection
>
> So it seems naturally to add also 'deselect'. Is there any reason for what
> it is not implemented yet? If none, can I implement it before 1.0.0? We can
> wait with gui behaviour changing for 1.0.1, but it would be good to have at
> least the methods ready in the 1.0.0 API.
>
> Regards,
> B.
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
--
Dr. Marco Hugentobler
Institute of Cartography
ETH Zurich
Technical Advisor QGIS Project Steering Committee
More information about the Qgis-developer
mailing list