greg
2/20/2008 2:16:00 PM
Thank you both for your replies.
I've found a workaround for now, it involves the ItemChecked in a ListView.
I was pulling values from a database row to set which items were selected in
a ListView when you went to modify this row. For some reason, after selecting
all those items (anItem.Checked = true;), when I re-enabled the ItemChecked
handler, it would get called for some reason, even though I was finished all
of the item checking. I would step through each .Checked=true; with the
debugger. I finished that portion of code, got to the portion where I
re-enabled the handler, and then all of a sudden the next step I would fnid
myself inside that event handler, when nothing has happened to cause it to
trigger.
What I've done is a work around by some intense googling :) I have a
MouseDown event which sets a boolean to true. The ItemChecked event checks
for this boolean and exits if it is false. That way when this event is
mysteriously called as mentioned above, it simply returns.