Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 355
  • Last Modified:

Workaround for wierd ListView behavior

Hi,

I am looking for a workaround for a wierd behavior, possibly a bug, that I am encountering with the .Net 2.0 ListView control. For some reason, when I have a list view with MultiSelect = false and I set the selected item before adding the ListView to a container control, the selected item gets cleared and then reset when the ListView is added to the container. This causes a problem because I am using the SelectedIndexChanged event to update an underlying data item, and it is causing unnecessary updates to occur. This can easily be reproduced in a clean project by creating a form and putting the following code in it.

public partial class Form1 : Form
    {
        public Form1()
        {
            InitializeComponent();

            ListView lv = new ListView();

            lv.MultiSelect = false;
            lv.Columns.Add("Test");
            lv.Items.Add("Test");
            lv.Items[0].Selected = true;

            lv.SelectedIndexChanged += ListView_SelectedIndexChanged;

            this.Controls.Add(lv);
           
        }

        private void ListView_SelectedIndexChanged(object sender, EventArgs e)
        {
            System.Diagnostics.Debug.Print("SelectedCount = {0}", ((ListView)sender).SelectedItems.Count);
        }
    }

Notice that if you run it, the event is fired 3 times, and the count is 1, then 0, then 1 again. All events are fired when the this.Controls.Add(lv) line is run.

Is there any way to work around this behavior other than to avoid setting the selected item until after the ListView is added to the container?

Thanks,
Zaphod.
0
Z_Beeblebrox
Asked:
Z_Beeblebrox
  • 4
  • 2
2 Solutions
 
Z_BeeblebroxAuthor Commented:
I found one workaround, it seems that OnCreateControl is not called until after the listview is done messing around with the selected item, so by ignoring all selected index changed events until after that is called, I can get the behavior I am looking for. Anyone have a better way?

Thanks,
Zaphod.
0
 
Expert1701Commented:
Why couldn't you just change the order?

i.e.:

  this.Controls.Add(lv);
  lv.Items[0].Selected = true;
  lv.SelectedIndexChanged += ListView_SelectedIndexChanged;
0
 
Z_BeeblebroxAuthor Commented:
Hi Expert1701,

Unfortunately, I can't really change the order, the control is being added to the container far away from the initialization code (the ListView is contained inside a UserControl), and it doesn't seem right for the code that is doing the adding to call something after it has done the adding so that the initialization can happen.

Thanks for the comment,
Zaphod.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
dkloeckCommented:
So what can you change? where can we add code?
0
 
dkloeckCommented:
you could change it to single selection after this.Controls.Add(lv);
then the event would only happen once
0
 
Z_BeeblebroxAuthor Commented:
Hi dkloeck,

I am inheriting from the ListView, so basically I can either change the behavior of the list view from within it, or change the design time properties, or respond to an event from the ListView.

I could change it to single selection afterwards, but I would need a place to do that. Right now, I only know of the OnCreateControl method.

Thanks,
Zaphod.
0
 
Z_BeeblebroxAuthor Commented:
Thanks for the input, in the end I went with the OnCreateControl method.

Zaphod.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now