[Mono-bugs] [Bug 81191][Wis] Changed - ListView with CheckBoxes = true and StateImageList with only one image should not remove the image...
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Fri Mar 30 04:40:17 EDT 2007
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 gert.driesen at pandora.be.
http://bugzilla.ximian.com/show_bug.cgi?id=81191
--- shadow/81191 2007-03-29 14:59:35.000000000 -0500
+++ shadow/81191.tmp.25537 2007-03-30 03:40:16.000000000 -0500
@@ -1,13 +1,13 @@
Bug#: 81191
Product: Mono: Class Libraries
Version: 1.2
OS: other
OS Details:
-Status: RESOLVED
-Resolution: FIXED
+Status: REOPENED
+Resolution:
Severity: Unknown
Priority: Wishlist
Component: Windows.Forms
AssignedTo: mkestner at ximian.com
ReportedBy: georgegiolfan at yahoo.com
QAContact: mono-bugs at ximian.com
@@ -73,6 +73,23 @@
cause the icon to be removed, but it does on Mono.
------- Additional Comments From mkestner at ximian.com 2007-03-29 14:59 -------
the reopen bug was because the image was being added after the
imagelist was set on the view. Added an internal ImageList.Changed
event to deal with the scenario on revision 75164.
+
+------- Additional Comments From gert.driesen at pandora.be 2007-03-30 03:40 -------
+On MS, a click on the state icon does not cause cause the Checked
+value to be changed if there's only a single image in the
+StateImageList. Double-clicking the state icon (or the item text)
+always causes the Checked value to be changed (regardless of the
+number of images in the StateImageList).
+
+Also, on MS the icon is not invalidated (retains the current icon)
+if the newly set imagelist does not have any images. But this is not
+a typical usage scenario, so I guess we can ignore this.
+
+On MS, setting the StateImageList to null after the ListView handle
+has been created causes the icon to be removed and does not cause it
+to be replaced by a checkbox, while on Mono it's replaced by a
+checkbox. I'm not saying we should change this, since I think the
+Mono behaviour makes more sense.
More information about the mono-bugs
mailing list