SelectionChanged event is fired twice and also fired when selection doesn't change.
Last Published: August 25, 2014No Product Found
Bug ID Number
NIM001172
Submitted
February 17, 2006
Last Modified
June 5, 2024
Applies to
No Product Found
Version found
9.0
Version Fixed
9.2
Status
Fixed
The bug has been fixed. See the Version Fixed and Additional Information, if applicable, for more information.
Workaround
This happens only the first time the feature selection is done and here is the reason why this happens:Map has two types of selections - Feature Selection and Graphic SelectionThe first time you select a feature, map first replacec the Graphic Selection with Feature Selection as its active selection - this is when it first fires the evern saying selection changed. Then it actually replaces the feature selection with the new selection. Once the Graphic selection is replaced by the feature selection, it no more fires this events twice. For 9x this is a known limit.