[Mono-bugs] [Bug 78848][Nor] Changed - Combobox does not handle multiple items with the same value correctly

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by latency at gmx.de.

http://bugzilla.ximian.com/show_bug.cgi?id=78848

--- shadow/78848	2006-08-27 07:55:05.000000000 -0400
+++ shadow/78848.tmp.19942	2006-08-27 08:03:25.000000000 -0400
@@ -39,6 +39,23 @@
 }
 
 ------- Additional Comments From latency at gmx.de  2006-08-27 07:55 -------
 Created an attachment (id=17526)
 Path proposal.
 
+
+------- Additional Comments From latency at gmx.de  2006-08-27 08:03 -------
+Better analysis of the bug:
+This behaviour is the result of the "item-centric" view of the
+ComboBox.  The original box tried to allocate the object index by it's
+position in the internal object collection. However, datasources like
+the one in the initial bug report result that The first and the second
+"A" are the same instance of the string. Therefore the "IndexOf" of
+the collection does not work since it allways finds the element at the
+first position regardless which index has be selected by the user.
+
+Patch changes the "item-centric" view of the ComboBox to a
+"index-centric" approach, which makes the combo-box useable. The only
+thing I know so far which differs from the MS implementation is that
+setting the DataSource raises the "SelectedIndexChanged" event 3 times
+. Where in MS implementation it is not being invoked until the first
+user-input.