Anyone: ListView Selected Index change seems to fire twice?

[n. Smith]

Hi All,
Is it normal that the ListView fires the selectedinexcha nge event
twice?

I have a LvLoaners list view item that updates 3 text boxes (code
below), when I click on an item. I have set MultiSelect to False.

The first click goes as planned, but all subsqequent clicks seem to
fire the event twice. The first firing triggers an ArgumentExcepti on,
resulting in nItem not being initialised. That's why I have the first
Catch Block.

Is this normal, or is something a little goofy?

-nick

Private Sub lvLoaners_Selec tedIndexChanged (ByVal sender As
System.Object, ByVal e As System.EventArg s) Handles
lvLoaners.Selec tedIndexChanged
Try

Dim nItem As Integer = lvLoaners.Selec tedIndices(0)

Dim lvItem As ListViewItem = lvLoaners.Items (nItem)

Me.txtEditLoane rName.Text = lvItem.SubItems (0).Text
Me.txtEditLoane rPhone.Text = lvItem.SubItems (1).Text
Me.txtEditLoane rEmail.Text = lvItem.SubItems (2).Text

Catch a As ArgumentExcepti on
Return

Catch ex As Exception
MessageBox.Show ("Error: " & ex.Message & " in
lvLoaners_Selec tedIndexChanged ()", "Error")

End Try

[Stephany Young]

Have you read the manual?

for the ListView.Select edIndexChanged event it says:

<quote>
In a multiple selection ListView control, this event occurs whenever an item
is removed or added to the list of selected items.
</quote>
"n. Smith" <ni***@yahoo.dk > wrote in message
news:g9******** *************** *********@4ax.c om...

Hi All,
Is it normal that the ListView fires the selectedinexcha nge event
twice?

I have a LvLoaners list view item that updates 3 text boxes (code
below), when I click on an item. I have set MultiSelect to False.

The first click goes as planned, but all subsqequent clicks seem to
fire the event twice. The first firing triggers an ArgumentExcepti on,
resulting in nItem not being initialised. That's why I have the first
Catch Block.

Is this normal, or is something a little goofy?

-nick

Private Sub lvLoaners_Selec tedIndexChanged (ByVal sender As
System.Object, ByVal e As System.EventArg s) Handles
lvLoaners.Selec tedIndexChanged
Try

Dim nItem As Integer = lvLoaners.Selec tedIndices(0)

Dim lvItem As ListViewItem = lvLoaners.Items (nItem)

Me.txtEditLoane rName.Text = lvItem.SubItems (0).Text
Me.txtEditLoane rPhone.Text = lvItem.SubItems (1).Text
Me.txtEditLoane rEmail.Text = lvItem.SubItems (2).Text

Catch a As ArgumentExcepti on
Return

Catch ex As Exception
MessageBox.Show ("Error: " & ex.Message & " in
lvLoaners_Selec tedIndexChanged ()", "Error")

End Try

[Herfried K. Wagner [MVP]]

"n. Smith" <ni***@yahoo.dk > schrieb:

Is it normal that the ListView fires the selectedinexcha nge event
twice?

I have a LvLoaners list view item that updates 3 text boxes (code
below), when I click on an item. I have set MultiSelect to False.

The first click goes as planned, but all subsqequent clicks seem to
fire the event twice. The first firing triggers an ArgumentExcepti on,
resulting in nItem not being initialised. That's why I have the first
Catch Block.

That's not a bug. It's a feature.

When the user initiates a selection change that effectively results in all
selected items being deselected and then one or more items being
(re)selected, the control will raise the event twice, first for deselecting
the items and then for selecting them again (although the user will only see
that as a single operation). You can avoid the exception by extending your
code like this:

\\\
Dim SourceControl As ListView = DirectCast(send er, ListView)
If SourceControl.S electedItems.Le ngth > 0 Then
...
End If
///

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

[n. Smith]

Mr Wagner,

Thanks a lot. An excellent solution.

Cheers,
Nick
On Tue, 3 May 2005 11:06:58 +0200, "Herfried K. Wagner [MVP]"
<hi************ ***@gmx.at> wrote:

"n. Smith" <ni***@yahoo.dk > schrieb:

Is it normal that the ListView fires the selectedinexcha nge event
twice?

I have a LvLoaners list view item that updates 3 text boxes (code
below), when I click on an item. I have set MultiSelect to False.

The first click goes as planned, but all subsqequent clicks seem to
fire the event twice. The first firing triggers an ArgumentExcepti on,
resulting in nItem not being initialised. That's why I have the first
Catch Block.

That's not a bug. It's a feature.

When the user initiates a selection change that effectively results in all
selected items being deselected and then one or more items being
(re)selected , the control will raise the event twice, first for deselecting
the items and then for selecting them again (although the user will only see
that as a single operation). You can avoid the exception by extending your
code like this:

\\\
Dim SourceControl As ListView = DirectCast(send er, ListView)
If SourceControl.S electedItems.Le ngth > 0 Then
...
End If
///