The event order is intentional, and there is a reason for it: in beforefeaturemodified listeners, you can return false if you don't want the selection to go away from the current feature.
Andreas. On Tue, Jul 9, 2013 at 8:56 AM, Sergey Kolosov <sergey.kolo...@gmail.com>wrote: > I'm migrating from OL 2.12 to OL 2.13. I used events 'featureselected' and > 'featureunselected' and they was triggered in intuitive way (in my opinion) > - first unselect selected feature and then select new one. Now with changes > in ModifyFeature control i switched to 'beforefeaturemodified' and > 'afterfeaturemodified' events. And they are triggered vice versa - > first 'beforefeaturemodified' and then 'afterfeaturemodified'. Not shure if > it is a problem, but i have some difficulties with such behavior. I can > handle it. I just want to know if it is right order of events triggering. > Thanks in advance. > > _______________________________________________ > Users mailing list > us...@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/openlayers-users > > -- Andreas Hocevar OpenGeo - http://opengeo.org/ Expert service straight from the developers.
_______________________________________________ Users mailing list us...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/openlayers-users
