Now this is an interesting question

[Jax]

I have this code, behold:

string message = "Are you sure? You will lose this
customer forever. (Well you'll have re-create from
scratch)";
string caption = "Delete";
MessageBoxButto ns buttons = MessageBoxButto ns.YesNo;
DialogResult result;
result = MessageBox.Show (this, message, caption, buttons);
if(result == DialogResult.Ye s)
{
foreach(ListVie wItem lvi in this.lstCustome rs.Items)
{
if(lvi.ImageInd ex == 1)
{
Customer c = (Customer)lvi.T ag;
alCustomers.Rem ove(c);
//this.lstCustome rs.Items.Remove (lvi);
break;
}
}
}
if(alCustomers. Count<1)
{
this.tabCustome rs.Visible = false;
}

Okay what this code does is delete the selected customer
(the one with image an image index of 1) removes the
ListViewItem from the listview then checks to see if there
are no customers left in the array list, if not it hides a
tab control.

What is entertaining is that if you go through this code
with the debugger and remove the slashed out line (where i
remove the listviewitem) alCustomers will never have a
count of zero.
It will for a little while until it hits the slashed out
line, at that point it regains the customer it previously
removed.
Anyone got any ideas why? (I'm assuming it's something to
do with the tag??)

Any help, as always, greatly appreciated, many smiles and
thanks to repliers.

jax

[Ignacio Machin \( .NET/ C# MVP \)]

Hi Jax,

Try this:

if(result == DialogResult.Ye s)
{
ListViewItem tobedeleted = null;
foreach(ListVie wItem lvi in this.lstCustome rs.Items)
{
if(lvi.ImageInd ex == 1)
{
Customer c = (Customer)lvi.T ag;
alCustomers.Rem ove(c);
tobedeleted = lvi;
break;
}
}
if ( tobedeleted != null )
this.lstCustome rs.Items.Remove ( tobedeleted);
}

Cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"Jax" <an*******@disc ussions.microso ft.com> wrote in message
news:00******** *************** *****@phx.gbl.. .

I have this code, behold:

string message = "Are you sure? You will lose this
customer forever. (Well you'll have re-create from
scratch)";
string caption = "Delete";
MessageBoxButto ns buttons = MessageBoxButto ns.YesNo;
DialogResult result;
result = MessageBox.Show (this, message, caption, buttons);
if(result == DialogResult.Ye s)
{
foreach(ListVie wItem lvi in this.lstCustome rs.Items)
{
if(lvi.ImageInd ex == 1)
{
Customer c = (Customer)lvi.T ag;
alCustomers.Rem ove(c);
//this.lstCustome rs.Items.Remove (lvi);
break;
}
}
}
if(alCustomers. Count<1)
{
this.tabCustome rs.Visible = false;
}

Okay what this code does is delete the selected customer
(the one with image an image index of 1) removes the
ListViewItem from the listview then checks to see if there
are no customers left in the array list, if not it hides a
tab control.

What is entertaining is that if you go through this code
with the debugger and remove the slashed out line (where i
remove the listviewitem) alCustomers will never have a
count of zero.
It will for a little while until it hits the slashed out
line, at that point it regains the customer it previously
removed.
Anyone got any ideas why? (I'm assuming it's something to
do with the tag??)

Any help, as always, greatly appreciated, many smiles and
thanks to repliers.

jax

[Jon Skeet [C# MVP]]

Jax <an*******@disc ussions.microso ft.com> wrote:

I have this code, behold:

<snip>

Could you produce a short but complete program which demonstrates the
problem? See http://www.pobox.com/~skeet/complete.html for what I mean.
It does look interesting, but I'd like to get a complete repro to start
with.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

I think that it may be either that he is modifying the collection that he
is iterating on:

foreach(ListVie wItem lvi in this.lstCustome rs.Items)
{
if(lvi.ImageInd ex == 1)
{
this.lstCustome rs.Items.Remove (lvi);
}
}
Or it may be also due that he is removing the selected element in the
ListView , and he may be handling the ListView.Select edIndexChanged event.

Jax:
Can you place a breakpoint in the ListView.Select edIndexChanged handler ?
( if used ). maybe there lay the answer.
Cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"Jon Skeet [C# MVP]" <sk***@pobox.co m> wrote in message
news:MP******** *************** *@msnews.micros oft.com...

Jax <an*******@disc ussions.microso ft.com> wrote:

I have this code, behold:

<snip>

Could you produce a short but complete program which demonstrates the
problem? See http://www.pobox.com/~skeet/complete.html for what I mean.
It does look interesting, but I'd like to get a complete repro to start
with.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

<"Ignacio Machin \( .NET/ C# MVP \)" <ignacio.mach in AT
dot.state.fl.us >> wrote:

I think that it may be either that he is modifying the collection that he
is iterating on:

Indeed - hadn't spotted that. I'd have expected to see an exception in
that case...

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Ignacio Machin \( .NET/ C# MVP \)]

Hi Jon,
"Jon Skeet [C# MVP]" <sk***@pobox.co m> wrote in message
news:MP******** *************** *@msnews.micros oft.com...

<"Ignacio Machin \( .NET/ C# MVP \)" <ignacio.mach in AT
dot.state.fl.us >> wrote:

I think that it may be either that he is modifying the collection that he is iterating on:
Indeed - hadn't spotted that. I'd have expected to see an exception in
that case...

Yes, I would expect that too, but Jax says nothing about an exception, so I
assume it does not happen.

Cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Jax]

Jon and Ingacio,

Thank you both so much for your replies, I find your input
very helpful.
Unfortunately this is a work problem and i'm now at home
without the code to hand.
I will post up a sample app on monday when I get back to
it.

As far as exceptions go there are none at all, it runs
without a problem.
My main concern is that in modifying the collection while
iterating through it I have messed up something somewhere
and this is a concern because i have used this code
(usually with arraylists or listboxes) quite a few times.
I assumed that the break keyword saved me from any
problems, is that generally the case?

I will try the new code that ingacio recommended, it
sounds a little bit like the fix I applied which was this:

if(result == DialogResult.Ye s)
{
foreach(ListVie wItem lvi in this.lstCustome rs.Items)
{
if(lvi.ImageInd ex == 1)
{
Customer c = (Customer)lvi.T ag;
alCustomers.Rem ove(c);
break;
}
}
if ( alCustomers.Cou nt == 0 )
this.lstCustome rs.Items.Clear( );
}

I'll get back to this on monday and see if it effects the
Arraylist when there is more then one customer as i'm not
certain that i've checked that out properly or not(i think
I have but i'll double check, which is why my fix only
applies to 0).

Thanks again, you're both a credit to this newsgroup :)

jax

-----Original Message-----
Hi Jon,
"Jon Skeet [C# MVP]" <sk***@pobox.co m> wrote in message
news:MP******* *************** **@msnews.micro soft.com...

<"Ignacio Machin \( .NET/ C# MVP \)" <ignacio.mach in AT
dot.state.fl.us >> wrote:

> I think that it may be either that he is modifying

the collection that

he > is iterating on:
Indeed - hadn't spotted that. I'd have expected to see an exception in that case...

Yes, I would expect that too, but Jax says nothing about

an exception, so Iassume it does not happen.

Cheers,

--
Ignacio Machin,
ignacio.mach in AT dot.state.fl.us
Florida Department Of Transportation

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

.

The problem was due to additional code in selected item
changed event.
I sorted it but thanks for your help :)

jax

-----Original Message-----
Jon and Ingacio,

Thank you both so much for your replies, I find your inputvery helpful.
Unfortunatel y this is a work problem and i'm now at home
without the code to hand.
I will post up a sample app on monday when I get back to
it.

As far as exceptions go there are none at all, it runs
without a problem.
My main concern is that in modifying the collection while
iterating through it I have messed up something somewhere
and this is a concern because i have used this code
(usually with arraylists or listboxes) quite a few times.
I assumed that the break keyword saved me from any
problems, is that generally the case?

I will try the new code that ingacio recommended, it
sounds a little bit like the fix I applied which was this:

if(result == DialogResult.Ye s)
{
foreach(ListVie wItem lvi in this.lstCustome rs.Items)
{
if(lvi.ImageInd ex == 1)
{
Customer c = (Customer)lvi.T ag;
alCustomers.Rem ove(c);
break;
}
}
if ( alCustomers.Cou nt == 0 )
this.lstCustome rs.Items.Clear( );
}

I'll get back to this on monday and see if it effects the
Arraylist when there is more then one customer as i'm not
certain that i've checked that out properly or not(i thinkI have but i'll double check, which is why my fix only
applies to 0).

Thanks again, you're both a credit to this newsgroup :)

jax

-----Original Message-----
Hi Jon,
"Jon Skeet [C# MVP]" <sk***@pobox.co m> wrote in message
news:MP****** *************** ***@msnews.micr osoft.com...

<"Ignacio Machin \( .NET/ C# MVP \)" <ignacio.mach in AT dot.state.fl.us >> wrote:
> I think that it may be either that he is modifyingthe collection that

he

> is iterating on:

Indeed - hadn't spotted that. I'd have expected to see

an exception in that case...

Yes, I would expect that too, but Jax says nothing

aboutan exception, so I

assume it does not happen.

Cheers,

--
Ignacio Machin,
ignacio.machi n AT dot.state.fl.us
Florida Department Of Transportation

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

.

.