Poor performace when selecting all items in a listbox?

[Duncan Smith]

So far, the quikest way I have found to select all items in a list box
is to turn off updates, set a wait cusror and then call SetSelected on
each item (see below), but it's too slow when the control is populated
with tens of thousands of items.

Ideally the wait-cursor shouldn't be needed as I hadn't anticipated a
select-all operation taking a noticeable amount of time. Has anyone
found a way to make this appear instantaneous as it would be in MFC?

Many thanks,

Duncan.

private void selectAllToolSt ripMenuItem_Cli ck(object sender, EventArgs
e)
{
if( Messages.Items. Count 0 )
{
Messages.BeginU pdate();

Cursor prevCursor = Cursor;
Cursor = Cursors.WaitCur sor;

for( int ii = 0; ii < Messages.Items. Count; ++ii )
{
Messages.SetSel ected(ii, true);
}

Messages.EndUpd ate();

Cursor = prevCursor;
}
}

[neelsmail]

On Jun 7, 1:18 pm, Duncan Smith <DSmith1...@goo glemail.comwrot e:

Has anyone found a way to make this appear instantaneous as it would be in MFC?

<snip>

for( int ii = 0; ii < Messages.Items. Count; ++ii )
{
Messages.SetSel ected(ii, true);
}

VERY new to C# and don't know Framework library (and therefore
implications) but following code worked much better for 5000 list
items/rows compared to "SetSelecte d"-

for( int ii = 0; ii < Messages.Items. Count; ++ii )
{
Messages.Select edIndex = ii;
}

Thanks,
Neel.

[not_a_commie]

You could try using a ListView instead of a ListBox.
Then replace
Messages.SetSel ected(ii, true);
with
Messages.Items[ii].Selected = true;
There are a few other properties you have to set on a ListView to make
it look like a ListBox. And the Items array is a different type of
object which is a bit of a pain.

for( int ii = 0; ii < Messages.Items. Count; ++ii )
{
Messages.Select edIndex = ii;
}

Um, I don't think that code snippet is quite the same as the original.
He wanted to select all, not select all one at a time.

[Duncan Smith]

On Jun 7, 12:59 pm, not_a_commie <notacom...@gma il.comwrote:

You could try using a ListView instead of a ListBox.
Then replace
Messages.SetSel ected(ii, true);
with
Messages.Items[ii].Selected = true;
There are a few other properties you have to set on a ListView to make
it look like a ListBox. And the Items array is a different type of
object which is a bit of a pain.

for( int ii = 0; ii < Messages.Items. Count; ++ii )
{
Messages.Select edIndex = ii;
}

Um, I don't think that code snippet is quite the same as the original.
He wanted to select all, not select all one at a time.

Thanks, I had to go with a ListView in the end anyway for the
EnsureVisible() method, so the most recently added item could be made
to be scrolled into view.

I found the quickest way to select all items was to use SendKeys(), I
hope it's not considered bad practice, certainly seems the most
responsive course given a densely populated control (see snippet
below):

Regards,

Duncan.

/// <summary>
/// Selects all items from the messages listview
/// </summary>
/// <param name="sender">C alling object</param>
/// <param name="e">args</param>
private void selectAllToolSt ripMenuItem_Cli ck(object sender,
EventArgs e)
{
if (Messages2.Item s.Count 0)
{
Messages2.Focus ();
SendKeys.SendWa it("{HOME}");
SendKeys.SendWa it("+{END}");
}
}

[neelsmail]

On Jun 7, 6:43 pm, Duncan Smith <DSmith1...@goo glemail.comwrot e:

I found the quickest way to select all items was to use SendKeys()

Yes, I had thought of that but I didn't know how to do that in new
framework (used of doing it in MFC), but, thanks to you, I know now.
In addition to that, the time that it takes to select _all_ items, no
matter how many, with HOME + END characters when done manually through
keyboard, didn't feel right. So, when with your example I tried it
with 10,000 items. With "Messages.Selec tedIndex = ii;", if you had a
event handler defined for "SelectedIndexC hanged" it will be called for
every item. But, with "SendKeys" it will be called _only_ for two
items (first and last). For some of the applications it would be okay,
for some of them its not I guess.

Thanks,
Neel.